Disclosure summary
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.
Source-reported weakness categories
CWE-401
Source-specific records & product guidance
Sources retain their own attribution and scoring. Follow the original record to confirm affected versions, fixed releases, and configuration conditions.
Microsoft Security Updates (CVRF) · 2026-Mar
Open original source · Updated Apr 08, 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.
Maximum of vendor-reported product scores; products and fixed builds are associations, not a universal affected-version statement.
Microsoft maximum product score: 5.3
| Vendor | Product / association | Version / bounds |
|---|---|---|
| Microsoft update guide | azl3 nodejs24 24.13.0-3 on Azure Linux 3.0 | (MSRC status code 3) |
| Microsoft update guide | azl3 nodejs 20.14.0-14 on Azure Linux 3.0 | (MSRC status code 3) |
Vendor remediation references
- CBL-Mariner Releases · build 24.14.1-1 · product IDs 21059-17084
- Vendor guidance · product IDs 21059-17084
- CBL-Mariner Releases · build 20.14.0-15 · product IDs 21111-17084
- Vendor guidance · product IDs 21111-17084
Original records & references
- NIST NVD record
- CVE Program record
- msrc.microsoft.com — Vendor advisory
PUBLISHED 2026-03-31T21:18:43-04:00
MODIFIED 2026-04-08T21:39:59-04:00
INGESTED 2026-10-08T12:45:08-04:00