Advisory
GHSA-5f7q-jpqc-wp7h
Also known as: CVE-2025-59472
Summary
Next.js has Unbounded Memory Consumption via PPR Resume Endpoint
Details
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:
- 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.
- 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, an application must run 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
Medium Basis: The source's own band: MODERATE
Dates
- Published
- 2026-01-28 15:20 UTC
- Modified
- 2026-09-10 03:50 UTC
Affected packages and fixes
| Package | Affected | Fix |
|---|---|---|
| next | introduced 16.0.0-beta.0, fixed 16.1.5 | npm install [email protected] |
| next | introduced 15.0.0-canary.0, last affected 15.0.0-canary.205 | No fixed version is listed. |
| next | introduced 15.0.1-canary.0, last affected 15.0.1-canary.3 | No fixed version is listed. |
| next | introduced 15.0.2-canary.0, last affected 15.0.2-canary.11 | No fixed version is listed. |
| next | introduced 15.0.3-canary.0, last affected 15.0.3-canary.9 | No fixed version is listed. |
| next | introduced 15.0.4-canary.0, last affected 15.0.4-canary.52 | No fixed version is listed. |
| next | introduced 15.1.1-canary.0, last affected 15.1.1-canary.27 | No fixed version is listed. |
| next | introduced 15.2.0-canary.0, last affected 15.2.0-canary.77 | No fixed version is listed. |
| next | introduced 15.2.1-canary.0, last affected 15.2.1-canary.6 | No fixed version is listed. |
| next | introduced 15.2.2-canary.0, last affected 15.2.2-canary.7 | No fixed version is listed. |
| next | introduced 15.3.0-canary.0, last affected 15.3.0-canary.46 | No fixed version is listed. |
| next | introduced 15.3.1-canary.0, last affected 15.3.1-canary.15 | No fixed version is listed. |
| next | introduced 15.4.0-canary.0, last affected 15.4.0-canary.130 | No fixed version is listed. |
| next | introduced 15.4.2-canary.0, last affected 15.4.2-canary.56 | No fixed version is listed. |
| next | introduced 15.5.1-canary.0, last affected 15.5.1-canary.39 | No fixed version is listed. |
| next | introduced 15.6.0-canary.0, fixed 15.6.0-canary.61 | npm install [email protected] |
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Links
Source
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0