cve.bz

CVE-2025-59472

7.5 highEPSS 0.4%

High (7.5) in vercel next.js. EPSS 0.4% chance of exploitation in the next 30 days. Fixed in next 15.6.0-canary.61, 16.1.5.

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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% chance of exploitation in the next 30 days; higher than 36% of CVEs (scores of 2026-10-31)
CWE
CWE-400
Published
Modified
Record from
the NVD, synced

Affected

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5f7q-jpqc-wp7hnpmnext>=16.0.0-beta.0 <16.1.516.1.5
GHSA-5f7q-jpqc-wp7hnpmnext>=15.0.0-canary.0 <=15.0.0-canary.205no fix published
GHSA-5f7q-jpqc-wp7hnpmnext>=15.0.1-canary.0 <=15.0.1-canary.3no fix published
GHSA-5f7q-jpqc-wp7hnpmnext>=15.0.2-canary.0 <=15.0.2-canary.11no fix published
GHSA-5f7q-jpqc-wp7hnpmnext>=15.0.3-canary.0 <=15.0.3-canary.9no fix published
GHSA-5f7q-jpqc-wp7hnpmnext>=15.0.4-canary.0 <=15.0.4-canary.52no fix published
GHSA-5f7q-jpqc-wp7hnpmnext>=15.1.1-canary.0 <=15.1.1-canary.27no fix published
GHSA-5f7q-jpqc-wp7hnpmnext>=15.2.0-canary.0 <=15.2.0-canary.77no fix published
GHSA-5f7q-jpqc-wp7hnpmnext>=15.2.1-canary.0 <=15.2.1-canary.6no fix published
GHSA-5f7q-jpqc-wp7hnpmnext>=15.2.2-canary.0 <=15.2.2-canary.7no fix published
GHSA-5f7q-jpqc-wp7hnpmnext>=15.3.0-canary.0 <=15.3.0-canary.46no fix published
GHSA-5f7q-jpqc-wp7hnpmnext>=15.3.1-canary.0 <=15.3.1-canary.15no fix published
GHSA-5f7q-jpqc-wp7hnpmnext>=15.4.0-canary.0 <=15.4.0-canary.130no fix published
GHSA-5f7q-jpqc-wp7hnpmnext>=15.4.2-canary.0 <=15.4.2-canary.56no fix published
GHSA-5f7q-jpqc-wp7hnpmnext>=15.5.1-canary.0 <=15.5.1-canary.39no fix published
GHSA-5f7q-jpqc-wp7hnpmnext>=15.6.0-canary.0 <15.6.0-canary.6115.6.0-canary.61

References

Check your stackJSON