VDB
Sign up
MEDIUM5.9

GHSA-5f7q-jpqc-wp7h

Next.js has Unbounded Memory Consumption via PPR Resume Endpoint

Quick fix

GHSA-5f7q-jpqc-wp7h — next: upgrade to the fixed version with the command below.

npm install next@16.1.5

Details

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, an application must run 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.

Are you affected?

Enter the version of the package you're using.

Affected packages

npm/next
Introduced in: 16.0.0-beta.0Fixed in: 16.1.5
Fixnpm install next@16.1.5
npm/next
Introduced in: 15.0.0-canary.0

No fixed version published yet for next (npm). Pin to a known-safe version or switch to an alternative.

npm/next
Introduced in: 15.0.1-canary.0

No fixed version published yet for next (npm). Pin to a known-safe version or switch to an alternative.

npm/next
Introduced in: 15.0.2-canary.0

No fixed version published yet for next (npm). Pin to a known-safe version or switch to an alternative.

npm/next
Introduced in: 15.0.3-canary.0

No fixed version published yet for next (npm). Pin to a known-safe version or switch to an alternative.

npm/next
Introduced in: 15.0.4-canary.0

No fixed version published yet for next (npm). Pin to a known-safe version or switch to an alternative.

npm/next
Introduced in: 15.1.1-canary.0

No fixed version published yet for next (npm). Pin to a known-safe version or switch to an alternative.

npm/next
Introduced in: 15.2.0-canary.0

No fixed version published yet for next (npm). Pin to a known-safe version or switch to an alternative.

npm/next
Introduced in: 15.2.1-canary.0

No fixed version published yet for next (npm). Pin to a known-safe version or switch to an alternative.

npm/next
Introduced in: 15.2.2-canary.0

No fixed version published yet for next (npm). Pin to a known-safe version or switch to an alternative.

npm/next
Introduced in: 15.3.0-canary.0

No fixed version published yet for next (npm). Pin to a known-safe version or switch to an alternative.

npm/next
Introduced in: 15.3.1-canary.0

No fixed version published yet for next (npm). Pin to a known-safe version or switch to an alternative.

npm/next
Introduced in: 15.4.0-canary.0

No fixed version published yet for next (npm). Pin to a known-safe version or switch to an alternative.

npm/next
Introduced in: 15.4.2-canary.0

No fixed version published yet for next (npm). Pin to a known-safe version or switch to an alternative.

npm/next
Introduced in: 15.5.1-canary.0

No fixed version published yet for next (npm). Pin to a known-safe version or switch to an alternative.

npm/next
Introduced in: 15.6.0-canary.0Fixed in: 15.6.0-canary.61
Fixnpm install next@15.6.0-canary.61

References