Description
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.
CVSS breakdown
CVSS 3.0
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low
Affected products
- nodejs / node20.20.1 – 20.20.1
- nodejs / node22.22.1 – 22.22.1
- nodejs / node24.14.0 – 24.14.0
- nodejs / node25.8.1 – 25.8.1
- nodejs / node.js20.20.1
Updated 5m ago · 8 sources