CVE-2025-59472Disclosure(vercel / next.js)

LOWCVSS 7.5 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

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

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-400

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • next.js

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • Technical details provided in 1 signal
  • Disclosure: 1 classified signal
  • 1 total mentions across 1 day

Affected systems

Vendors
Products
next.js

1 version affected across 1 product

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-01-28: 1Technical Details · 2026-01-28: 101-28
Signal classification1 categories
Disclosure
1100.0%
Referenced assets1 URL
By indicator
Full discourse1 post
  • cvereports@_cvereports
    Disclosure

    CVE-2025-59472: Next.js PPR: When 'Minimal Mode' Maximizes Your Downtime A Denial of Service (DoS) vulnerability exists in Next.js versions utilizing Partial Prerendering (PPR) in 'minimal mode'. An unauthenticated attacker can exploit the 'resume' en... https://cvereports.com/reports/CVE-2025-59472

    Post summary

    The article discloses a Denial‑of‑Service vulnerability in Next.js’s Partial Prerendering minimal mode, providing some technical exploitation details, but no evidence of active attacks or mitigation.

    0000043
    29 followersView on X
CPE platform detail63 entries

63 of 63 entries

PartVendorProductVersionTarget SWTarget HW
Appvercelnext.js-node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-
Appvercelnext.js15.6.0node.js-

Explore more