Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2025-59472

next: NextJS Denial of Service in Partial Pre Rendering

Overview

Published
26 Jan 2026
Modified
17 Jun 2026
High CVE
3 Registry packages
18 OS packages
3 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
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

Weakness: CWE-400

Affected packages · 3

Packages affected by CVE-2025-59472
EcosystemPackageVulnerableFixed in
npm next >=16.0.0-beta.0, <16.1.5>=15.0.0-canary.0, <=15.0.0-canary.205>=15.0.1-canary.0, <=15.0.1-canary.3>=15.0.2-canary.0, <=15.0.2-canary.11>=15.0.3-canary.0, <=15.0.3-canary.9+11 more 16.1.515.6.0-canary.61
Seal npm @seal-security/next >=16.0.6-sp1, <16.0.6-sp999 16.0.6-sp999
Seal npm next >=16.0.6-sp0, <16.0.6-sp999 16.0.6-sp999

Open a package to see all its vulnerabilities.

Operating systems · 7 fixes

Red Hat 3 releases · 2 packages

affected 3
firefox aspnetcore-runtime-7-0
Red Hat fixes for CVE-2025-59472
ReleasePackageFixed in
7 firefox affected
8 firefox +1 affected
9 aspnetcore-runtime-7-0 +14 affected

chainguard 1 release · 2 packages

fixed 2
jitsucom-jitsu langfuse-3
chainguard fixes for CVE-2025-59472
ReleasePackageFixed in
jitsucom-jitsu 2.11.0-r14
langfuse-3 +1 3.150.0-r0

wolfi 1 release · 2 packages

fixed 2
jitsucom-jitsu langfuse-3
wolfi fixes for CVE-2025-59472
ReleasePackageFixed in
jitsucom-jitsu 2.11.0-r14
langfuse-3 3.150.0-r0

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.