Next.js next-resume Connection Exhaustion DoS
CVE-2026-44579 is a denial-of-service vulnerability in Next.js affecting versions before 15.5.16 and 16.2.5. It impacts applications using Partial Prerendering via the Cache Components feature. Crafted POST requests to a server action can trigger a request-body handling deadlock associated with the Next-Resume mechanism used for resuming Partial Prerendered requests. In affected configurations, the deadlock leaves connections open for an extended period instead of completing or failing promptly, causing accumulation of open connections and file descriptor consumption until the service becomes unavailable to legitimate users.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Next-Resume header before they reach Next.js, for example at the edge, reverse proxy, WAF, or load balancer. Because the header is intended to be internal-only, rejecting or stripping it from untrusted client traffic reduces exposure. Additional rate limiting and connection/request timeout controls may help reduce DoS impact, but the primary mitigation in the provided content is blocking the Next-Resume header from external clients.Remediation
Patch, then assume compromise.
Exploits
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
7 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.