next · denial of service
cve-program · CVE-2025-59472
PublishedA 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.
Read the publisher's advisoryeuvd · EUVD-2025-206333
PublishedA 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.
Read the publisher's advisorynvd · CVE-2025-59472
PublishedA 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.
Read the publisher's advisoryosv · GHSA-5f7q-jpqc-wp7h
PublishedA 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.
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2025-59472
PublishedA 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 …
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.
- Source published
- 26 Jan 2026 21:43:05 UTC
- Source modified
- 27 Jan 2026 14:54:04 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
euvd · EUVD-2025-206333
PublishedA 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 …
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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Jan 26, 2026, 9:43:05 PM
dateUpdated: Jan 27, 2026, 2:54:04 PM
1 related source bulletins · separate from aliases
WID-SEC-W-2026-0219: Vercel Next.js: Mehrere Schwachstellen ermöglichen Denial of Service
CVE-2025-59471 · CVE-2025-59472 · CVE-2026-23864
- Source published
- Jan 26, 2026, 9:43:05 PM (timezone not stated)
- Source modified
- Jan 27, 2026, 2:54:04 PM (timezone not stated)
- Saved here
- 15 Nov 2026 04:38:38 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd · CVE-2025-59472
PublishedA 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 …
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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-400
Original publisher date fields
published: 2026-01-26T22:15:53.027
lastModified: 2026-06-17T09:46:13.337
63 source CPE criteria · context only
- cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:-:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary0:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary1:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary10:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary11:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary12:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary13:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary14:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary15:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary16:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary17:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary18:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary19:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary2:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary20:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary21:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary22:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary23:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary24:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary25:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary26:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary27:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary28:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary29:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary3:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary30:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary31:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary32:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary33:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary34:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary35:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary36:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary37:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary38:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary39:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary4:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary40:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary41:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary42:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary43:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary44:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary45:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary46:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary47:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary48:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary49:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary5:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary50:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary51:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary52:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary53:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary54:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary55:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary56:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary57:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary58:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary59:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary6:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary60:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary7:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary8:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.6.0:canary9:*:*:*:node.js:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 26 Jan 2026 22:15:53 UTC
- Source modified
- 17 Jun 2026 09:46:13 UTC
- Saved here
- 25 Oct 2026 03:17:27 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 3.1 · [email protected] · Primary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
osv · GHSA-5f7q-jpqc-wp7h
PublishedNext.js has Unbounded Memory Consumption via PPR Resume Endpoint
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.
- Source published
- 28 Jan 2026 15:20:55 UTC
- Source modified
- 10 Sep 2026 03:50:32 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Publisher rating · MODERATE