GHSA-5f7q-jpqc-wp7h Next.js has Unbounded Memory Consumption via PPR Resume Endpoint

• npm next: >= 16.0.0-beta.0, < 16.1.5 → fixed in 16.1.5 • npm next: >= 15.0.0-canary.0, <= 15.0.0-canary.205 (no fix yet) • npm next: >= 15.0.1-canary.0, <= 15.0.1-canary.3 (no fix yet) • npm next: >= 15.0.2-canary.0, <= 15.0.2-canary.11 (no fix yet) • npm next: >= 15.0.3-canary.0, <= 15.0.3-canary.9 (no fix yet) • npm next: >= 15.0.4-canary.0, <= 15.0.4-canary.52 (no fix yet) • npm next: >= 15.1.1-canary.0, <= 15.1.1-canary.27 (no fix yet) • npm next: >= 15.2.0-canary.0, <= 15.2.0-canary.77 (no fix yet) • npm next: >= 15.2.1-canary.0, <= 15.2.1-canary.6 (no fix yet) • npm next: >= 15.2.2-canary.0, <= 15.2.2-canary.7 (no fix yet) • npm next: >= 15.3.0-canary.0, <= 15.3.0-canary.46 (no fix yet) • npm next: >= 15.3.1-canary.0, <= 15.3.1-canary.15 (no fix yet) • npm next: >= 15.4.0-canary.0, <= 15.4.0-canary.130 (no fix yet) • npm next: >= 15.4.2-canary.0, <= 15.4.2-canary.56 (no fix yet) • npm next: >= 15.5.1-canary.0, <= 15.5.1-canary.39 (no fix yet) • npm next: >= 15.6.0-canary.0, < 15.6.0-canary.61 → fixed in 15.6.0-canary.61

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.