dbcve.org
Next.jsApplication · Vercel

CVE-2025-59472

HIGH · 7.5 CVSS v3.1 Published 2026-01-26
Fix available
A fix is available. Upgrade to 15.6.0 / 16.1.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Next.js with Partial Prerendering (PPR) enabled in minimal mode has two memory exhaustion vulnerabilities: unbounded POST request body buffering via Buffer.concat() without size limits, and unbounded decompression using inflateSync() that allows zipbombs to expand dramatically. Both cause fatal V8 out-of-memory errors, crashing the Node.js process.

MitigationUpgrade to Next.js 15.6.0-canary.61 or 16.1.5 which contains fixes for both unbounded buffering and decompression vulnerabilities. Until upgraded, disable PPR/cached components or avoid running in minimal mode.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Next.jsApplication
Affected:>= 15.0.0, < 15.6.0>= 16.0.0, < 16.1.5= 15.6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check your Next.js version
    Run `npm list next` or inspect package.json to find the installed Next.js version number
    Affected if The version falls within >= 15.0.0 and < 15.6.0, equals 15.6.0, or falls within >= 16.0.0 and < 16.1.5
  2. Locate your Next.js configuration file
    Find next.config.js, next.config.mjs, or next.config.ts in your project root
    Affected if A Next.js config file exists and the following checks can be performed
  3. Verify if PPR is enabled
    Open your Next.js config file and search for `ppr` under the `experimental` object, for example: `experimental: { ppr: true }` or `experimental: { ppr: '...' }`
    Affected if The `ppr` property is set to any value (true, 'incremental', 'by-request', or similar) in the experimental config
  4. Confirm if minimal mode is configured
    In the same config file, check if ppr is set to 'minimal' or if there is an explicit minimal mode flag, for example: `experimental: { ppr: 'minimal' }`
    Affected if PPR is configured with 'minimal' mode or a similar minimal setting that enables the vulnerable code path

You are affected if your Next.js version is in the vulnerable range AND PPR with minimal mode is enabled in your configuration, allowing unbounded request body buffering and decompression to trigger out-of-memory crashes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 15.6.0 / 16.1.5 or later
Fixed in 15.6.016.1.5
Interim mitigation

Upgrade to Next.js 15.6.0-canary.61 or 16.1.5 which contains fixes for both unbounded buffering and decompression vulnerabilities. Until upgraded, disable PPR/cached components or avoid running in minimal mode.

Recommended fix High confidence

16.1.5

  1. 1. Identify all Next.js application instances running with `experimental.ppr: true` or `cacheComponents: true` configuration.
  2. 2. Ensure `NEXT_PRIVATE_MINIMAL_MODE=1` environment variable is not set in production (this is a debugging/internal flag).
  3. 3. If PPR is required, upgrade Next.js to version 16.1.5 (or 15.6.0-canary.61 for the 15.x line).
  4. 4. Update package.json dependency: `npm install [email protected]` or `yarn add [email protected]`.
  5. 5. Rebuild and redeploy all affected application instances.
  6. 6. Verify the application functions correctly after upgrade by testing PPR-enabled pages.
Caveat Review Next.js 16.1.5 release notes for any breaking changes between your current version and 16.1.5, particularly around PPR behavior and cache handling.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Next.js Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,520
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,432.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59472 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59472 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data