Node
Node.js is vulnerable to HTTP/2 response memory disclosure via a use-after-free during stream teardown
A use-after-free in Node.js HTTP/2 stream teardown can leak response memory, including the contents of other connections' response buffers, to a peer. When a stream is torn down while a write is still backpressured, for example by a peer RST_STREAM or by the server's own per-stream timeout destroying the stream, the stream's response buffer is freed but a reference to it is still used, so freed or unrelated heap memory is written to the socket instead of the intended response. On Node.js 26.x and 24.x the teardown can be driven purely by a remote peer once the window-size change from 26.9.0 and 24.22.0 is present, and on all supported lines the same defect is reachable through an application-initiated teardown such as a per-stream idle timeout. 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.