Next.js has Unbounded Memory Consumption via PPR Resume Endpoint
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.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | next | >= 16.0.0-beta.0, < 16.1.5, >= 15.0.0-canary.0, <= 15.0.0-canary.205, >= 15.0.1-canary.0, <= 15.0.1-canary.3, >= 15.0.2-canary.0, <= 15.0.2-canary.11, >= 15.0.3-canary.0, <= 15.0.3-canary.9, >= 15.0.4-canary.0, <= 15.0.4-canary.52, >= 15.1.1-canary.0, <= 15.1.1-canary.27, >= 15.2.0-canary.0, <= 15.2.0-canary.77, >= 15.2.1-canary.0, <= 15.2.1-canary.6, >= 15.2.2-canary.0, <= 15.2.2-canary.7, >= 15.3.0-canary.0, <= 15.3.0-canary.46, >= 15.3.1-canary.0, <= 15.3.1-canary.15, >= 15.4.0-canary.0, <= 15.4.0-canary.130, >= 15.4.2-canary.0, <= 15.4.2-canary.56, >= 15.5.1-canary.0, <= 15.5.1-canary.39, >= 15.6.0-canary.0, < 15.6.0-canary.61 | 16.1.5, 15.6.0-canary.61 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H- Weakness (CWE)
CWE-400, CWE-409, CWE-770- Platform
- npm
- Package
next- Disclosed
- 28.01.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-5f7q-jpqc-wp7h - CC BY 4.0
Vulnerability history: next
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 73
- First → latest
- 12.2017 10.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 5
- High 27
- Medium 32
- Low 9
Disclosures per year
- 2017: 1
- 2018: 2
- 2019: 0
- 2020: 3
- 2021: 3
- 2022: 3
- 2023: 1
- 2024: 6
- 2025: 14
- 2026: 40
-
Next.js has Unbounded Memory Consumption via PPR Resume Endpoint this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.