CVE-2025-59472 Next.js has Unbounded Memory Consumption via PPR Resume Endpoint
Attackers can crash Next.js servers via memory exhaustion in PPR minimal mode using unbounded buffering or zipbomb payloads.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-59472?
CVE-2025-59472 is a medium-severity denial of service vulnerability in Vercel Next.js, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-400
Which versions are affected by CVE-2025-59472?
32 open source packages ship an affected version, including next. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
next npm | From 15.0.0-canary.0 to 15.0.0-canary.205 | None |
next npm | From 15.0.0-canary.0 to 15.0.0-canary.205 | None |
next npm | From 15.0.1-canary.0 to 15.0.1-canary.3 | None |
next npm | From 15.0.1-canary.0 to 15.0.1-canary.3 | None |
next npm | From 15.0.2-canary.0 to 15.0.2-canary.11 | None |
next npm | From 15.0.2-canary.0 to 15.0.2-canary.11 | None |
26 more packages
next npm | From 15.0.3-canary.0 to 15.0.3-canary.9 | None |
next npm | From 15.0.3-canary.0 to 15.0.3-canary.9 | None |
next npm | From 15.0.4-canary.0 to 15.0.4-canary.52 | None |
next npm | From 15.0.4-canary.0 to 15.0.4-canary.52 | None |
next npm | From 15.1.1-canary.0 to 15.1.1-canary.27 | None |
next npm | From 15.1.1-canary.0 to 15.1.1-canary.27 | None |
next npm | From 15.2.0-canary.0 to 15.2.0-canary.77 | None |
next npm | From 15.2.0-canary.0 to 15.2.0-canary.77 | None |
next npm | From 15.2.1-canary.0 to 15.2.1-canary.6 | None |
next npm | From 15.2.1-canary.0 to 15.2.1-canary.6 | None |
next npm | From 15.2.2-canary.0 to 15.2.2-canary.7 | None |
next npm | From 15.2.2-canary.0 to 15.2.2-canary.7 | None |
next npm | From 15.3.0-canary.0 to 15.3.0-canary.46 | None |
next npm | From 15.3.0-canary.0 to 15.3.0-canary.46 | None |
next npm | From 15.3.1-canary.0 to 15.3.1-canary.15 | None |
next npm | From 15.3.1-canary.0 to 15.3.1-canary.15 | None |
next npm | From 15.4.0-canary.0 to 15.4.0-canary.130 | None |
next npm | From 15.4.0-canary.0 to 15.4.0-canary.130 | None |
next npm | From 15.4.2-canary.0 to 15.4.2-canary.56 | None |
next npm | From 15.4.2-canary.0 to 15.4.2-canary.56 | None |
next npm | From 15.5.1-canary.0 to 15.5.1-canary.39 | None |
next npm | From 15.5.1-canary.0 to 15.5.1-canary.39 | None |
next npm | From 15.6.0-canary.0 | 15.6.0-canary.61 |
next npm | From 15.6.0-canary.0 | 15.6.0-canary.61 |
next npm | From 16.0.0-beta.0 | 16.1.5 |
next npm | From 16.0.0-beta.0 | 16.1.5 |
Products include Vercel Next.js.
How do I fix CVE-2025-59472?
Upgrade next to a fixed version for your release line: 15.6.0-canary.61 or 16.1.5.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2025-59472 being exploited?
There is no known exploitation of CVE-2025-59472 in the wild and no public exploit code.
Other vulnerabilities in Vercel Next.js
- CVE-2025-29927 Authorization Bypass in Next.js Middleware
- CVE-2026-44578 Next.js: Server-side request forgery in applications using WebSocket upgrades
- CVE-2026-94483 Next.js: Server-Side Request Forgery in Image Optimization
- CVE-2026-64642 Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale
- CVE-2026-64645 Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname
Sources
Also known as CLSA-2026-1792195720, CLSA-2026-1792196709, CLSA-2026-1792206280, CLSA-2026-1792272215, CLSA-2026-1792292989, CLSA-2026-1792304703 and 5 more.