Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.42% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2025-59472High confidence
A denial of service vulnerability exists in Next.js versions with Partial Prerendering (PPR) enabled when running in minimal mode
vercel · next
Official source article: GitHub GHSA-5F7Q-JPQC-WP7H ↗. Check the applicable product and release in the original source.
5.9MediumCVSS 3.1
Scheduled
Fix not verifiedMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs vercel next and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Open-source package ranges32 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| npmnext | >= 16.0.0-beta.0, < 16.1.5 | 16.1.5 | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.6.0-canary.0, < 15.6.0-canary.61 | 15.6.0-canary.61 | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.0.0-canary.0, <= 15.0.0-canary.205 | Not stated | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.0.1-canary.0, <= 15.0.1-canary.3 | Not stated | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.0.2-canary.0, <= 15.0.2-canary.11 | Not stated | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.0.3-canary.0, <= 15.0.3-canary.9 | Not stated | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.0.4-canary.0, <= 15.0.4-canary.52 | Not stated | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.1.1-canary.0, <= 15.1.1-canary.27 | Not stated | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.2.0-canary.0, <= 15.2.0-canary.77 | Not stated | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.2.1-canary.0, <= 15.2.1-canary.6 | Not stated | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.2.2-canary.0, <= 15.2.2-canary.7 | Not stated | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.3.0-canary.0, <= 15.3.0-canary.46 | Not stated | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.3.1-canary.0, <= 15.3.1-canary.15 | Not stated | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.4.0-canary.0, <= 15.4.0-canary.130 | Not stated | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.4.2-canary.0, <= 15.4.2-canary.56 | Not stated | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | >= 15.5.1-canary.0, <= 15.5.1-canary.39 | Not stated | GitHub advisory ↗upstream repository advisory · 8 Apr 2026 |
| npmnext | SEMVER: introduced 16.0.0-beta.0; fixed 16.1.5 | 16.1.5 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.0.0-canary.0; last affected 15.0.0-canary.205 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.0.1-canary.0; last affected 15.0.1-canary.3 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.0.2-canary.0; last affected 15.0.2-canary.11 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.0.3-canary.0; last affected 15.0.3-canary.9 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.0.4-canary.0; last affected 15.0.4-canary.52 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.1.1-canary.0; last affected 15.1.1-canary.27 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.2.0-canary.0; last affected 15.2.0-canary.77 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.2.1-canary.0; last affected 15.2.1-canary.6 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.2.2-canary.0; last affected 15.2.2-canary.7 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.3.0-canary.0; last affected 15.3.0-canary.46 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.3.1-canary.0; last affected 15.3.1-canary.15 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.4.0-canary.0; last affected 15.4.0-canary.130 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.4.2-canary.0; last affected 15.4.2-canary.56 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.5.1-canary.0; last affected 15.5.1-canary.39 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmnext | SEMVER: introduced 15.6.0-canary.0; fixed 15.6.0-canary.61 | 15.6.0-canary.61 | OSV record ↗aggregator derived · 10 Sep 2026 |
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Fix not verified01
What, why and how
A denial of service vulnerability exists in Next.js versions with Partial Prerendering (PPR) enabled when running in minimal mode. The PPR resume endpoint accepts unauthenticated POST requests with the `Next-Resume: 1` header and processes attacker-controlled postponed state data. Two closely related vulnerabilities allow an attacker to crash the server process through memory exhaustion: 1. **Unbounded request body buffering**: The server buffers the entire POST request body into memory using `Buffer.concat()` without enforcing any size limit, allowing arbitrarily large payloads to exhaust available memory. 2. **Unbounded decompression (zipbomb)**: The resume data cache is decompressed using `inflateSync()` without limiting the decompressed output size. A small compressed payload can expand to hundreds of megabytes or gigabytes, causing memory exhaustion. Both attack vectors result in a fatal V8 out-of-memory error (`FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory`) causing the Node.js process to terminate. The zipbomb variant is particularly dangerous as it can bypass reverse proxy request size limits while still causing large memory allocation on the server. To be affected you must have an application running with `experimental.ppr: true` or `cacheComponents: true` configured along with the NEXT_PRIVATE_MINIMAL_MODE=1 environment variable. Strongly consider upgrading to 15.6.0-canary.61 or 16.1.5 to reduce risk and prevent availability issues in Next applications.
What
A denial of service vulnerability exists in Next.js versions with Partial Prerendering (PPR) enabled when running in minimal mode. The PPR resume endpoint accepts unauthenticated POST requests with the `Next-Resume: 1` header and processes attacker-controlled postponed state data. Two closely related vulnerabilities allow an attacker to crash the server process through memory exhaustion: 1. **Unbounded request body buffering**: The server buffers the entire POST request body into memory using `Buffer.concat()` without enforcing any size limit, allowing arbitrarily large payloads to exhaust available memory. 2. **Unbounded decompression (zipbomb)**: The resume data cache is decompressed using `inflateSync()` without limiting the decompressed output size. A small compressed payload can expand to hundreds of megabytes or gigabytes, causing memory exhaustion. Both attack vectors result in a fatal V8 out-of-memory error (`FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory`) causing the Node.js process to terminate. The zipbomb variant is particularly dangerous as it can bypass reverse proxy request size limits while still causing large memory allocation on the server. To be affected you must have an application running with `experimental.ppr: true` or `cacheComponents: true` configured along with the NEXT_PRIVATE_MINIMAL_MODE=1 environment variable. Strongly consider upgrading to 15.6.0-canary.61 or 16.1.5 to reduce risk and prevent availability issues in Next applications.
Why
The product does not properly control the allocation and maintenance of a limited resource.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
What
A denial of service vulnerability exists in Next.js versions with Partial Prerendering (PPR) enabled when running in minimal mode. The PPR resume endpoint accepts unauthenticated POST requests with the `Next-Resume: 1` header and processes attacker-controlled postponed state data. Two closely related vulnerabilities allow an attacker to crash the server process through memory exhaustion: 1. **Unbounded request body buffering**: The server buffers the entire POST request body into memory using `Buffer.concat()` without enforcing any size limit, allowing arbitrarily large payloads to exhaust available memory. 2. **Unbounded decompression (zipbomb)**: The resume data cache is decompressed using `inflateSync()` without limiting the decompressed output size. A small compressed payload can expand to hundreds of megabytes or gigabytes, causing memory exhaustion. Both attack vectors result in a fatal V8 out-of-memory error (`FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory`) causing the Node.js process to terminate. The zipbomb variant is particularly dangerous as it can bypass reverse proxy request size limits while still causing large memory allocation on the server. To be affected you must have an application running with `experimental.ppr: true` or `cacheComponents: true` configured along with the NEXT_PRIVATE_MINIMAL_MODE=1 environment variable. Strongly consider upgrading to 15.6.0-canary.61 or 16.1.5 to reduce risk and prevent availability issues in Next applications.
Why
The product does not properly control the allocation and maintenance of a limited resource.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Uncontrolled Resource Consumption → disrupt the affected service
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-400 ↗
CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix not verified
- Affected
- next: 15.0.0-canary.0 < 15.0.0, 15.0.1-canary.0 < 15.0.1, 15.0.2-canary.0 < 15.0.2, 15.0.3-canary.0 < 15.0.3, 15.0.4-canary.0 < 15.0.4, 15.1.0-canary.0 < 15.1.0, 15.1.1-canary.0 < 15.1.1, 15.1.2-canary.0 < 15.1.2, 15.1.3-canary.0 < 15.1.3, 15.1.4-canary.0 < 15.1.4, 15.1.5-canary.0 < 15.1.5, 15.1.6-canary.0 < 15.1.6, 15.1.7-canary.0 < 15.1.7, 15.2.0-canary.0 < 15.2.0, 15.2.1-canary.0 < 15.2.1, 15.2.2-canary.0 < 15.2.2, 15.2.3-canary.0 < 15.2.3, 15.2.4-canary.0 < 15.2.4, 15.2.5-canary.0 < 15.2.5, 15.3.0-canary.0 < 15.3.0, 15.3.1-canary.0 < 15.3.1, 15.3.2-canary.0 < 15.3.2, 15.1.8-canary.0 < 15.1.8, 15.3.3-canary.0 < 15.3.3, 15.4.0-canary.0 < 15.4.0, 15.3.4-canary.0 < 15.3.4, 15.3.5-canary.0 < 15.3.5, 15.4.1-canary.0 < 15.4.1, 15.4.2-canary.0 < 15.4.2, 15.4.3-canary.0 < 15.4.3, 15.4.4-canary.0 < 15.4.4, 15.4.5-canary.0 < 15.4.5, 15.4.6-canary.0 < 15.4.6, 15.4.7-canary.0 < 15.4.7, 15.5.0-canary.0 < 15.5.0, 15.5.1-canary.0 < 15.5.1, 15.5.2-canary.0 < 15.5.2, 15.5.3-canary.0 < 15.5.3, 15.5.4-canary.0 < 15.5.4, 15.5.5-canary.0 < 15.5.5, 15.5.6-canary.0 < 15.5.6, 15.5.7-canary.0 < 15.5.7, 15.4.8-canary.0 < 15.4.8, 15.1.9-canary.0 < 15.1.9, 15.0.5-canary.0 < 15.0.5, 15.3.6-canary.0 < 15.3.6, 15.2.6-canary.0 < 15.2.6, 15.5.8-canary.0 < 15.5.8, 15.4.9-canary.0 < 15.4.9, 15.3.7-canary.0 < 15.3.7, 15.2.7-canary.0 < 15.2.7, 15.1.10-canary.0 < 15.1.10, 15.0.6-canary.0 < 15.0.6, 15.5.9-canary.0 < 15.5.9, 15.4.10-canary.0 < 15.4.10, 15.3.8-canary.0 < 15.3.8, 15.2.8-canary.0 < 15.2.8, 15.1.11-canary.0 < 15.1.11, 15.0.7-canary.0 < 15.0.7, 16.1.0 < 16.1.5
- Fixed
- No fixed version is explicitly recorded in the structured CVE data.
- Action
- No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 26 Jan 2026 · Last source change 27 Jan 2026, 14:54 UTC · CWE-400 · Uncontrolled Resource Consumption
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2025-206333
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.