CVE-2026-44579: CWE-770: Allocation of Resources Without Limits or Throttling in vercel next.js
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.
AI Analysis
Technical Summary
CVE-2026-44579 affects Next.js, a React framework, in versions before 15.5.16 and 16.2.5 when using Partial Prerendering through the Cache Components feature. A maliciously crafted POST request to a server action can trigger a deadlock in request-body handling, causing connections to remain open for extended periods. This leads to exhaustion of file descriptors and server capacity, resulting in denial of service for legitimate users. The vulnerability is categorized under CWE-770 (Allocation of Resources Without Limits or Throttling) and CWE-833 (Deadlock). The issue has been fixed in Next.js versions 15.5.16 and 16.2.5. No known exploits in the wild have been reported. The vendor advisory from Red Hat confirms the vulnerability and references the fixed versions.
Potential Impact
Successful exploitation can cause denial of service by exhausting server resources such as file descriptors and connection capacity. This prevents legitimate users from accessing the affected Next.js application. There is no impact on confidentiality or integrity reported. The vulnerability specifically affects server-side handling of POST requests in certain Next.js configurations.
Mitigation Recommendations
Upgrade Next.js to version 15.5.16 or 16.2.5 or later, where this vulnerability is fixed. Since this is not a cloud service, users must apply the patch themselves. Patch status is confirmed by the vendor advisory. No alternative mitigations or temporary fixes are indicated in the advisory.
CVE-2026-44579: CWE-770: Allocation of Resources Without Limits or Throttling in vercel next.js
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.
CVSS v3.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-44579 affects Next.js, a React framework, in versions before 15.5.16 and 16.2.5 when using Partial Prerendering through the Cache Components feature. A maliciously crafted POST request to a server action can trigger a deadlock in request-body handling, causing connections to remain open for extended periods. This leads to exhaustion of file descriptors and server capacity, resulting in denial of service for legitimate users. The vulnerability is categorized under CWE-770 (Allocation of Resources Without Limits or Throttling) and CWE-833 (Deadlock). The issue has been fixed in Next.js versions 15.5.16 and 16.2.5. No known exploits in the wild have been reported. The vendor advisory from Red Hat confirms the vulnerability and references the fixed versions.
Potential Impact
Successful exploitation can cause denial of service by exhausting server resources such as file descriptors and connection capacity. This prevents legitimate users from accessing the affected Next.js application. There is no impact on confidentiality or integrity reported. The vulnerability specifically affects server-side handling of POST requests in certain Next.js configurations.
Mitigation Recommendations
Upgrade Next.js to version 15.5.16 or 16.2.5 or later, where this vulnerability is fixed. Since this is not a cloud service, users must apply the patch themselves. Patch status is confirmed by the vendor advisory. No alternative mitigations or temporary fixes are indicated in the advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-06T21:49:12.424Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-44579","vendor":"Red Hat"}]
Threat ID: 6a04ba22cbff5d8610f482d8
Added to database: 05/13/2026, 17:51:30 UTC
Last enriched: 07/15/2026, 13:10:24 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 78
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.