Skip to content

Denial of Service in Partial Pre Rendering

Moderate
andresriancho published GHSA-5f7q-jpqc-wp7h Jan 26, 2026

Package

npm next (npm)

Affected versions

15.0.0-canary.0
15.0.1-canary.0
15.0.2-canary.0
15.0.3-canary.0
15.0.4-canary.0
15.1.0-canary.0
15.1.1-canary.0
15.1.2-canary.0
15.1.3-canary.0
15.1.4-canary.0
15.1.5-canary.0
15.1.6-canary.0
15.1.7-canary.0
15.2.0-canary.0
15.2.1-canary.0
15.2.2-canary.0
15.2.3-canary.0
15.2.4-canary.0
15.2.5-canary.0
15.3.0-canary.0
15.3.1-canary.0
15.3.2-canary.0
15.1.8-canary.0
15.3.3-canary.0
15.4.0-canary.0
15.3.4-canary.0
15.3.5-canary.0
15.4.1-canary.0
15.4.2-canary.0
15.4.3-canary.0
15.4.4-canary.0
15.4.5-canary.0
15.4.6-canary.0
15.4.7-canary.0
15.5.0-canary.0
15.5.1-canary.0
15.5.2-canary.0
15.5.3-canary.0
15.5.4-canary.0
15.5.5-canary.0
15.5.6-canary.0
15.5.7-canary.0
15.4.8-canary.0
15.1.9-canary.0
15.0.5-canary.0
15.3.6-canary.0
15.2.6-canary.0
15.5.8-canary.0
15.4.9-canary.0
15.3.7-canary.0
15.2.7-canary.0
15.1.10-canary.0
15.0.6-canary.0
15.5.9-canary.0
15.4.10-canary.0
15.3.8-canary.0
15.2.8-canary.0
15.1.11-canary.0
15.0.7-canary.0
16.1.0

Patched versions

15.0.0
15.0.1
15.0.2
15.0.3
15.0.4
15.1.0
15.1.1
15.1.2
15.1.3
15.1.4
15.1.5
15.1.6
15.1.7
15.2.0
15.2.1
15.2.2
15.2.3
15.2.4
15.2.5
15.3.0
15.3.1
15.3.2
15.1.8
15.3.3
15.4.0
15.3.4
15.3.5
15.4.1
15.4.2
15.4.3
15.4.4
15.4.5
15.4.6
15.4.7
15.5.0
15.5.1
15.5.2
15.5.3
15.5.4
15.5.5
15.5.6
15.5.7
15.4.8
15.1.9
15.0.5
15.3.6
15.2.6
15.5.8
15.4.9
15.3.7
15.2.7
15.1.10
15.0.6
15.5.9
15.4.10
15.3.8
15.2.8
15.1.11
15.0.7
16.1.5

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.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

CVE ID

CVE-2025-59472

Weaknesses

Allocation of Resources Without Limits or Throttling

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. Learn more on MITRE.