CVE-2026-21714: Vulnerability in nodejs node
A memory leak vulnerability exists in Node. js HTTP/2 servers when clients send WINDOW_UPDATE frames on stream 0 that cause the flow control window to exceed the maximum allowed value. Although the server sends a GOAWAY frame correctly, the associated Http2Session object is not cleaned up, leading to resource leakage. This affects Node. js versions 20. 20. 1, 22. 22. 1, 24. 14.
AI Analysis
Technical Summary
CVE-2026-21714 describes a memory leak in Node.js HTTP/2 servers triggered by clients sending WINDOW_UPDATE frames on the connection-level stream (stream 0) that cause the flow control window to exceed the maximum 2³¹-1 value. While the server responds with a GOAWAY frame to terminate the connection, it fails to properly clean up the Http2Session object, resulting in a memory leak. This issue affects multiple recent Node.js versions (20.20.1, 22.22.1, 24.14.0, 25.8.1). The vulnerability is categorized under CWE-401 (Improper Release of Memory). There is no indication of known exploits in the wild or a vendor-provided patch at this time.
Potential Impact
The vulnerability leads to a memory leak on affected Node.js HTTP/2 servers, which can degrade availability by exhausting server resources over time. There is no impact on confidentiality or integrity. The medium severity rating (CVSS 5.3) reflects the potential for denial of service through resource exhaustion but no direct compromise of data or system control.
Mitigation Recommendations
Patch status is not yet confirmed as no official patch or remediation link is provided. Users should monitor the Node.js project advisories for updates. Until a fix is available, consider limiting exposure of HTTP/2 services or implementing resource monitoring and automated restarts to mitigate potential memory exhaustion. Avoid relying on generic mitigations not directly related to this specific memory leak.
CVE-2026-21714: Vulnerability in nodejs node
Description
A memory leak vulnerability exists in Node. js HTTP/2 servers when clients send WINDOW_UPDATE frames on stream 0 that cause the flow control window to exceed the maximum allowed value. Although the server sends a GOAWAY frame correctly, the associated Http2Session object is not cleaned up, leading to resource leakage. This affects Node. js versions 20. 20. 1, 22. 22. 1, 24. 14.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-21714 describes a memory leak in Node.js HTTP/2 servers triggered by clients sending WINDOW_UPDATE frames on the connection-level stream (stream 0) that cause the flow control window to exceed the maximum 2³¹-1 value. While the server responds with a GOAWAY frame to terminate the connection, it fails to properly clean up the Http2Session object, resulting in a memory leak. This issue affects multiple recent Node.js versions (20.20.1, 22.22.1, 24.14.0, 25.8.1). The vulnerability is categorized under CWE-401 (Improper Release of Memory). There is no indication of known exploits in the wild or a vendor-provided patch at this time.
Potential Impact
The vulnerability leads to a memory leak on affected Node.js HTTP/2 servers, which can degrade availability by exhausting server resources over time. There is no impact on confidentiality or integrity. The medium severity rating (CVSS 5.3) reflects the potential for denial of service through resource exhaustion but no direct compromise of data or system control.
Mitigation Recommendations
Patch status is not yet confirmed as no official patch or remediation link is provided. Users should monitor the Node.js project advisories for updates. Until a fix is available, consider limiting exposure of HTTP/2 services or implementing resource monitoring and automated restarts to mitigate potential memory exhaustion. Avoid relying on generic mitigations not directly related to this specific memory leak.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2026-01-04T15:00:06.574Z
- Cvss Version
- 3.0
- State
- PUBLISHED
Threat ID: 69cacda7e6bfc5ba1d6188ab
Added to database: 3/30/2026, 7:23:19 PM
Last enriched: 4/7/2026, 10:50:49 AM
Last updated: 5/14/2026, 10:03:58 PM
Views: 90
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.
External Links
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.