CVE-2026-21714: 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.
Medium CVSS 5.3
- CVE id
- CVE-2026-21714
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Node.js Runtimes and servers |
<= 20.20.1 >= 22.0.0, <= 22.22.1 >= 24.0.0, <= 24.14.0 >= 25.0.0, <= 25.8.1 |
after 20.20.1, 22.22.1, 24.14.0, 25.8.1 |
How to fix it
Upgrade Node.js to a release newer than the last affected update of the line you run (20.20.1, 22.22.1, 24.14.0, 25.8.1).
node --version
- Install the patched Node.js release of your major line (nvm install, or the node image tag) everywhere the app runs and builds.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.