CVE-2026-44579: vercel next.js · Unthrottled Resource Allocation
Affects vercel next.jsSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 16.2.5 or 15.5.16 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 16.2.5, 15.5.16
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade next.js and next to 16.2.5 or 15.5.16.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vercelnext.js | Affected
| Fixed in
|
| vercelnext.js | Affected
| Fixed in
|
npmnextpkg:npm/nextOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Next.js versions 15.5.16 and 16.2.5. Users should upgrade to these or later versions to remediate the vulnerability. According to the Red Hat advisory, no effective mitigation other than upgrading is currently available or meets their criteria for ease of use and applicability. Therefore, upgrading is the recommended remediation.
Description
Next.js is a React framework for building full-stack web applications. From to before 15.5.16 and 16.2.5, applications using Partial Prerendering through the Cache Components feature can be vulnerable to connection exhaustion through crafted POST requests to a server action. In affected configurations, a malicious request can trigger a request-body handling deadlock that leaves connections open for an extended period, consuming file descriptors and server capacity until legitimate users are denied service. This vulnerability is fixed in 15.5.16 and 16.2.5.
References
- github.com/vercel/next.js/security/advisories/GHSA-mg66-mrh9-m8jx (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-44579 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2477193 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44579.json (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:37272 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:34608 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:40974 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:54435 (opens in a new tab)