CVE-2026-21714
Published:March 30, 2026
Updated:May 18, 2026
A memory leak occurs in Node.js HTTP/2 servers when a client sends WINDOW_UPDATE frames on stream 0 (connection-level) that cause the flow control window to exceed the maximum value of 2³¹-1. The server correctly sends a GOAWAY frame, but the Http2Session object is never cleaned up. This vulnerability affects HTTP2 users on Node.js 20, 22, 24 and 25.
Affected Packages
https://github.com/nodejs/node.git (GITHUB):
Affected version(s) >=v20.0.0 <v20.20.2Fix Suggestion:
Update to version v20.20.2https://github.com/nodejs/node.git (GITHUB):
Affected version(s) >=v22.0.0 <v22.22.2Fix Suggestion:
Update to version v22.22.2https://github.com/nodejs/node.git (GITHUB):
Affected version(s) >=v24.0.0 <v24.14.1Fix Suggestion:
Update to version v24.14.1https://github.com/nodejs/node.git (GITHUB):
Affected version(s) >=v25.0.0 <v25.8.2Fix Suggestion:
Update to version v25.8.2Related Resources (1)
Do you need more information?
Contact UsCVSS v4
Base Score:
6.9
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
NONE
Privileges Required
NONE
User Interaction
NONE
Vulnerable System Confidentiality
NONE
Vulnerable System Integrity
NONE
Vulnerable System Availability
LOW
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
5.3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Weakness Type (CWE)
Missing Release of Memory after Effective Lifetime
EPSS
Base Score:
0.02