# 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. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 Jan 2026 - **Updated:** 27 Jan 2026 - **Also known as:** CLSA-2026-1792195720, CLSA-2026-1792196709, CLSA-2026-1792206280, CLSA-2026-1792272215, CLSA-2026-1792292989, CLSA-2026-1792304703, CLSA-2026-1792326285, CLSA-2026-1792338225, CLSA-2026-1792358578, CLSA-2026-1792363970, GHSA-5f7q-jpqc-wp7h ## 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 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2025-59472? 32 open source packages ship an affected version, including next. It affects 1 product. | Package | Ecosystem | 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 | | `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: 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. ## 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](https://insights.sbomify.com/CVE-2025-29927/): Authorization Bypass in Next.js Middleware (critical 9.1) - [CVE-2026-44578](https://insights.sbomify.com/CVE-2026-44578/): Next.js: Server-side request forgery in applications using WebSocket upgrades (high 8.6) - [CVE-2026-94483](https://insights.sbomify.com/CVE-2026-94483/): Next.js: Server-Side Request Forgery in Image Optimization (high 8.3) - [CVE-2026-64642](https://insights.sbomify.com/CVE-2026-64642/): Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale (high 8.3) - [CVE-2026-64645](https://insights.sbomify.com/CVE-2026-64645/): Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname (high 8.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-59472 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2025-59472 in the wild and no public exploit code. Affected packages and fixed versions: - next (npm): affected from 15.0.0-canary.0 up to 15.0.0-canary.205; no fix listed - next (npm): affected from 15.0.0-canary.0 up to 15.0.0-canary.205; no fix listed - next (npm): affected from 15.0.1-canary.0 up to 15.0.1-canary.3; no fix listed - next (npm): affected from 15.0.1-canary.0 up to 15.0.1-canary.3; no fix listed - next (npm): affected from 15.0.2-canary.0 up to 15.0.2-canary.11; no fix listed - next (npm): affected from 15.0.2-canary.0 up to 15.0.2-canary.11; no fix listed - next (npm): affected from 15.0.3-canary.0 up to 15.0.3-canary.9; no fix listed - next (npm): affected from 15.0.3-canary.0 up to 15.0.3-canary.9; no fix listed - next (npm): affected from 15.0.4-canary.0 up to 15.0.4-canary.52; no fix listed - next (npm): affected from 15.0.4-canary.0 up to 15.0.4-canary.52; no fix listed - next (npm): affected from 15.1.1-canary.0 up to 15.1.1-canary.27; no fix listed - next (npm): affected from 15.1.1-canary.0 up to 15.1.1-canary.27; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-59472/ (Markdown: https://insights.sbomify.com/CVE-2025-59472/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59472 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59472 - OSV: https://osv.dev/vulnerability/CVE-2025-59472 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-59472/ Summaries are generated and may contain mistakes; the official description above is the record.