High Denial of service

CVE-2025-59472 — Uncontrolled Resource Consumption in Vercel Next

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.

Published Jan 26, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: hackerone

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.4% (30-day exploitation probability)+5
Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.42%

ahead of 34% of scored CVEs · Oct 14, 2026

Affects

Vercel

Next and 1 more

CVSS base

7.5

High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Vercel Next, Vercel Next.js).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Vercel	Next	≥ 15.4.10-canary.0 and < 15.4.10≥ 15.3.8-canary.0 and < 15.3.8≥ 15.2.8-canary.0 and < 15.2.8≥ 15.1.11-canary.0 and < 15.1.11≥ 15.0.7-canary.0 and < 15.0.7≥ 16.1.0 and < 16.1.5≥ 15.0.0-canary.0 and < 15.0.0≥ 15.0.1-canary.0 and < 15.0.1 and 52 more ≥ 15.0.2-canary.0 and < 15.0.2≥ 15.0.3-canary.0 and < 15.0.3≥ 15.0.4-canary.0 and < 15.0.4≥ 15.1.0-canary.0 and < 15.1.0≥ 15.1.1-canary.0 and < 15.1.1≥ 15.1.2-canary.0 and < 15.1.2≥ 15.1.3-canary.0 and < 15.1.3≥ 15.1.4-canary.0 and < 15.1.4≥ 15.1.5-canary.0 and < 15.1.5≥ 15.1.6-canary.0 and < 15.1.6≥ 15.1.7-canary.0 and < 15.1.7≥ 15.2.0-canary.0 and < 15.2.0≥ 15.2.1-canary.0 and < 15.2.1≥ 15.2.2-canary.0 and < 15.2.2≥ 15.2.3-canary.0 and < 15.2.3≥ 15.2.4-canary.0 and < 15.2.4≥ 15.2.5-canary.0 and < 15.2.5≥ 15.3.0-canary.0 and < 15.3.0≥ 15.3.1-canary.0 and < 15.3.1≥ 15.3.2-canary.0 and < 15.3.2≥ 15.1.8-canary.0 and < 15.1.8≥ 15.3.3-canary.0 and < 15.3.3≥ 15.4.0-canary.0 and < 15.4.0≥ 15.3.4-canary.0 and < 15.3.4≥ 15.3.5-canary.0 and < 15.3.5≥ 15.4.1-canary.0 and < 15.4.1≥ 15.4.2-canary.0 and < 15.4.2≥ 15.4.3-canary.0 and < 15.4.3≥ 15.4.4-canary.0 and < 15.4.4≥ 15.4.5-canary.0 and < 15.4.5≥ 15.4.6-canary.0 and < 15.4.6≥ 15.4.7-canary.0 and < 15.4.7≥ 15.5.0-canary.0 and < 15.5.0≥ 15.5.1-canary.0 and < 15.5.1≥ 15.5.2-canary.0 and < 15.5.2≥ 15.5.3-canary.0 and < 15.5.3≥ 15.5.4-canary.0 and < 15.5.4≥ 15.5.5-canary.0 and < 15.5.5≥ 15.5.6-canary.0 and < 15.5.6≥ 15.5.7-canary.0 and < 15.5.7≥ 15.4.8-canary.0 and < 15.4.8≥ 15.1.9-canary.0 and < 15.1.9≥ 15.0.5-canary.0 and < 15.0.5≥ 15.3.6-canary.0 and < 15.3.6≥ 15.2.6-canary.0 and < 15.2.6≥ 15.5.8-canary.0 and < 15.5.8≥ 15.4.9-canary.0 and < 15.4.9≥ 15.3.7-canary.0 and < 15.3.7≥ 15.2.7-canary.0 and < 15.2.7≥ 15.1.10-canary.0 and < 15.1.10≥ 15.0.6-canary.0 and < 15.0.6≥ 15.5.9-canary.0 and < 15.5.9	Vulnerable	CVE Program (cve.org) e CISA ADP
Vercel	Next.js	≥ 15.0.0 and < 15.6.0≥ 16.0.0 and < 16.1.5version 15.6.0version 15.6.0-canary0version 15.6.0-canary1version 15.6.0-canary10version 15.6.0-canary11version 15.6.0-canary12 and 56 more version 15.6.0-canary13version 15.6.0-canary14version 15.6.0-canary15version 15.6.0-canary16version 15.6.0-canary17version 15.6.0-canary18version 15.6.0-canary19version 15.6.0-canary2version 15.6.0-canary20version 15.6.0-canary21version 15.6.0-canary22version 15.6.0-canary23version 15.6.0-canary24version 15.6.0-canary25version 15.6.0-canary26version 15.6.0-canary27version 15.6.0-canary28version 15.6.0-canary29version 15.6.0-canary3version 15.6.0-canary30version 15.6.0-canary31version 15.6.0-canary32version 15.6.0-canary33version 15.6.0-canary34version 15.6.0-canary35version 15.6.0-canary36version 15.6.0-canary37version 15.6.0-canary38version 15.6.0-canary39version 15.6.0-canary4version 15.6.0-canary40version 15.6.0-canary41version 15.6.0-canary42version 15.6.0-canary43version 15.6.0-canary44version 15.6.0-canary45version 15.6.0-canary46version 15.6.0-canary47version 15.6.0-canary48version 15.6.0-canary49version 15.6.0-canary5version 15.6.0-canary50version 15.6.0-canary51version 15.6.0-canary52version 15.6.0-canary53version 15.6.0-canary54version 15.6.0-canary55version 15.6.0-canary56version 15.6.0-canary57version 15.6.0-canary58version 15.6.0-canary59version 15.6.0-canary6version 15.6.0-canary60version 15.6.0-canary7version 15.6.0-canary8version 15.6.0-canary9	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.5	CVSS 3.1	High	3.9	3.6	nvd@nist.gov via NIST National Vulnerability Database
5.9	CVSS 3.1	Medium	2.2	3.6	support@hackerone.com via NIST National Vulnerability Database
5.9	CVSS 3.1	Medium	—	—	hackerone via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 7.5 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-400 · Uncontrolled Resource Consumption

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.42%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Track CPU/memory spikes and availability drops correlated with request patterns.

web/proxy/WAF logsnetwork IDS/IPSresource metrics

Timeline

What happened to this CVE, newest first.

2026
Affected products added · vercel/next
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 7.5
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Jan 26, 2026 · hackerone

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

github.com/vercel/next.js/security/advisories/GHSA-5f7q-jpqc-wp7h
Vendor Advisory, NIST National Vulnerability Database

Elsewhere on this site

Vercel
every CVE for this vendor

Denial of service
same class

CWE-400
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2026-94543 Next.js: Cache poisoning of SSG and ISR pages in self-hosted Next.js applications 13d
Medium CVE-2026-94483 Next.js: Server-Side Request Forgery in Image Optimization 13d
Medium CVE-2026-64649 Server-Side Request Forgery (SSRF) in Vercel Next.js Jul 27, 2026
Medium CVE-2026-64648 Next.js is a React framework for building full-stack web applications. In versions… Jul 27, 2026
Medium CVE-2026-64646 Allocation of Resources Without Limits or Throttling in Vercel Next.js Jul 27, 2026
Medium CVE-2026-64647 Improper Encoding or Escaping of Output in Vercel Next.js Jul 27, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-59472 is "Uncontrolled Resource Consumption in Vercel Next", rated High. It affects Next (Vercel); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 0.42% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.