Node
Node.js is vulnerable to an HTTP/2 memory and file-descriptor leak via a protocol error during session shutdown
An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never notices, leaving a dangling session: the socket stays in CLOSE_WAIT and all of Node.js's HTTP/2 state for that connection is held in memory indefinitely, with no further cost to the attacker. The attacker can start the shutdown remotely by sending GOAWAY(NO_ERROR), so it is reliable against default HTTP/2 servers. It is an incomplete-fix case of CVE-2026-48937: that fix detected nghttp2 internal terminations by watching for GOAWAY sent while not shutting down, but missed terminations that arrive while the session is already shutting down. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0.0.0, < 22.23.5
- >= 23.0.0, < 24.22.3
- >= 25.0.0, < 26.13.1
Fixed in 22.23.5, 24.22.3, 26.13.1
Mitigation
Upgrade node to 22.23.5 or 24.22.3 or 26.13.1 or later.
References
- Vendor advisory nodejs.org/en/blog/vulnerability/november-2026…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.