A denial of service vulnerability exists in Next.js versions with Partial Prerendering (PPR) enabled when running in minimal mode.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 15.0.0, 15.0.1, 15.0.2, 15.0.3, 15.0.4, and 56 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- vercel next
From 15.0.0-canary.0 · fixed in 15.0.0; From 15.0.1-canary.0 · fixed in 15.0.1; From 15.0.2-canary.0 · fixed in 15.0.2; From 15.0.3-canary.0 · fixed in 15.0.3; From 15.0.4-canary.0 · fixed in 15.0.4; From 15.1.0-canary.0 · fixed in 15.1.0; From 15.1.1-canary.0 · fixed in 15.1.1; From 15.1.2-canary.0 · fixed in 15.1.2; From 15.1.3-canary.0 · fixed in 15.1.3; From 15.1.4-canary.0 · fixed in 15.1.4; From 15.1.5-canary.0 · fixed in 15.1.5; From 15.1.6-canary.0 · fixed in 15.1.6; From 15.1.7-canary.0 · fixed in 15.1.7; From 15.2.0-canary.0 · fixed in 15.2.0; From 15.2.1-canary.0 · fixed in 15.2.1; From 15.2.2-canary.0 · fixed in 15.2.2; From 15.2.3-canary.0 · fixed in 15.2.3; From 15.2.4-canary.0 · fixed in 15.2.4; From 15.2.5-canary.0 · fixed in 15.2.5; From 15.3.0-canary.0 · fixed in 15.3.0; From 15.3.1-canary.0 · fixed in 15.3.1; From 15.3.2-canary.0 · fixed in 15.3.2; From 15.1.8-canary.0 · fixed in 15.1.8; From 15.3.3-canary.0 · fixed in 15.3.3; From 15.4.0-canary.0 · fixed in 15.4.0; From 15.3.4-canary.0 · fixed in 15.3.4; From 15.3.5-canary.0 · fixed in 15.3.5; From 15.4.1-canary.0 · fixed in 15.4.1; From 15.4.2-canary.0 · fixed in 15.4.2; From 15.4.3-canary.0 · fixed in 15.4.3; From 15.4.4-canary.0 · fixed in 15.4.4; From 15.4.5-canary.0 · fixed in 15.4.5; From 15.4.6-canary.0 · fixed in 15.4.6; From 15.4.7-canary.0 · fixed in 15.4.7; From 15.5.0-canary.0 · fixed in 15.5.0; From 15.5.1-canary.0 · fixed in 15.5.1; From 15.5.2-canary.0 · fixed in 15.5.2; From 15.5.3-canary.0 · fixed in 15.5.3; From 15.5.4-canary.0 · fixed in 15.5.4; From 15.5.5-canary.0 · fixed in 15.5.5; From 15.5.6-canary.0 · fixed in 15.5.6; From 15.5.7-canary.0 · fixed in 15.5.7; From 15.4.8-canary.0 · fixed in 15.4.8; From 15.1.9-canary.0 · fixed in 15.1.9; From 15.0.5-canary.0 · fixed in 15.0.5; From 15.3.6-canary.0 · fixed in 15.3.6; From 15.2.6-canary.0 · fixed in 15.2.6; From 15.5.8-canary.0 · fixed in 15.5.8; From 15.4.9-canary.0 · fixed in 15.4.9; From 15.3.7-canary.0 · fixed in 15.3.7; From 15.2.7-canary.0 · fixed in 15.2.7; From 15.1.10-canary.0 · fixed in 15.1.10; From 15.0.6-canary.0 · fixed in 15.0.6; From 15.5.9-canary.0 · fixed in 15.5.9; From 15.4.10-canary.0 · fixed in 15.4.10; From 15.3.8-canary.0 · fixed in 15.3.8; From 15.2.8-canary.0 · fixed in 15.2.8; From 15.1.11-canary.0 · fixed in 15.1.11; From 15.0.7-canary.0 · fixed in 15.0.7; From 16.1.0 · fixed in 16.1.5
- nextnpm
From 16.0.0-beta.0 · fixed in 16.1.5
- nextnpm
From 15.0.0-canary.0 · through 15.0.0-canary.205
- nextnpm
From 15.0.1-canary.0 · through 15.0.1-canary.3
- nextnpm
From 15.0.2-canary.0 · through 15.0.2-canary.11
- nextnpm
From 15.0.3-canary.0 · through 15.0.3-canary.9
- nextnpm
From 15.0.4-canary.0 · through 15.0.4-canary.52
- nextnpm
From 15.1.1-canary.0 · through 15.1.1-canary.27
- nextnpm
From 15.2.0-canary.0 · through 15.2.0-canary.77
- nextnpm
From 15.2.1-canary.0 · through 15.2.1-canary.6
- nextnpm
From 15.2.2-canary.0 · through 15.2.2-canary.7
- nextnpm
From 15.3.0-canary.0 · through 15.3.0-canary.46
- nextnpm
From 15.3.1-canary.0 · through 15.3.1-canary.15
- nextnpm
From 15.4.0-canary.0 · through 15.4.0-canary.130
- nextnpm
From 15.4.2-canary.0 · through 15.4.2-canary.56
- nextnpm
From 15.5.1-canary.0 · through 15.5.1-canary.39
- nextnpm
From 15.6.0-canary.0 · fixed in 15.6.0-canary.61