CVE-2025-59472

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.

Published: 2026-01-26 Last update: 2026-02-24 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-59472 is rated Low Risk (36/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.15%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-59472

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-28 0.05% 0.15% +0.10%
2 2026-02-01 0.04% 0.05% +0.01%
3 2026-01-27 — 0.04% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-59472

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.9 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 3.6 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2025-59472

GitHub Security Advisory for CVE-2025-59472

GHSA-5f7q-jpqc-wp7h · Severity: medium · Ecosystem: npm — Next.js has Unbounded Memory Consumption via PPR Resume Endpoint

OS Trackers for CVE-2025-59472

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2025-59472

Affected software / configurations for CVE-2025-59472

Vendor Product Version Raw CPE
vercel next.js >= 15.0.0, < 15.6.0 cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
vercel next.js >= 16.0.0, < 16.1.5 cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:-:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary0:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary1:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary10:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary11:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary12:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary13:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary14:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary15:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary16:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary17:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary18:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary19:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary2:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary20:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary21:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary22:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary23:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary24:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary25:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary26:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary27:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary28:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary29:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary3:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary30:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary31:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary32:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary33:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary34:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary35:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary36:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary37:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary38:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary39:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary4:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary40:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary41:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary42:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary43:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary44:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary45:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary46:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary47:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary48:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary49:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary5:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary50:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary51:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary52:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary53:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary54:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary55:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary56:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary57:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary58:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary59:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary6:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary60:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary7:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary8:*:*:*:node.js:*:*
vercel next.js 15.6.0 cpe:2.3:a:vercel:next.js:15.6.0:canary9:*:*:*:node.js:*:*

References for CVE-2025-59472

cvelogic Threat Intelligence