CVE-2025-59472: 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: 1.
Published Jan 28, 2026 · Updated Apr 8, 2026
Affected packages
next
- Ecosystem
- npm
- Affected
- >= 16.0.0-beta.0, < 16.1.5
- Fixed in
- 16.1.5
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.6.0-canary.0, < 15.6.0-canary.61
- Fixed in
- 15.6.0-canary.61
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.0.0-canary.0, <= 15.0.0-canary.205
- Fixed in
- No patched version yet
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.0.1-canary.0, <= 15.0.1-canary.3
- Fixed in
- No patched version yet
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.0.2-canary.0, <= 15.0.2-canary.11
- Fixed in
- No patched version yet
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.0.3-canary.0, <= 15.0.3-canary.9
- Fixed in
- No patched version yet
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.0.4-canary.0, <= 15.0.4-canary.52
- Fixed in
- No patched version yet
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.1.1-canary.0, <= 15.1.1-canary.27
- Fixed in
- No patched version yet
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.2.0-canary.0, <= 15.2.0-canary.77
- Fixed in
- No patched version yet
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.2.1-canary.0, <= 15.2.1-canary.6
- Fixed in
- No patched version yet
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.2.2-canary.0, <= 15.2.2-canary.7
- Fixed in
- No patched version yet
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.3.0-canary.0, <= 15.3.0-canary.46
- Fixed in
- No patched version yet
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.3.1-canary.0, <= 15.3.1-canary.15
- Fixed in
- No patched version yet
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.4.0-canary.0, <= 15.4.0-canary.130
- Fixed in
- No patched version yet
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.4.2-canary.0, <= 15.4.2-canary.56
- Fixed in
- No patched version yet
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.5.1-canary.0, <= 15.5.1-canary.39
- Fixed in
- No patched version yet
- Check
npm ls next
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to cylewaitforit, jesvinjames.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-119346
Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes
medium6.0Nov 19, 2026CVE-2026-119347
Next.js: SVG rejection bypass in the image optimization
medium6.9Nov 19, 2026CVE-2026-119348
Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
medium6.3Nov 19, 2026CVE-2026-119349
Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments
medium6.3Nov 19, 2026CVE-2026-119350
Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params
medium6.3Nov 19, 2026CVE-2026-119351
Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata
medium6.3Nov 17, 2026
