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.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 5.9, indicating it can be exploited remotely over the network but requires specific conditions to be met without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts and availability (service disruption) for affected systems. Impacting 1 product from vercel organizations running these solutions should prioritize assessment and patching.
Reported in 2026, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2026-01-26T22:15:53.027
2026-02-24T18:24:35.830
Analyzed
CVSSv3.1: 5.9 (MEDIUM)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | vercel | next.js | < 15.6.0 | Yes |
| Application | vercel | next.js | < 16.1.5 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
| Application | vercel | next.js | 15.6.0 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For vercel's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.