Threat intelligence · CVEs & news
Published: 11/11/2026 · Modified: 11/16/2026
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.
No confirmed-exploitation catalog lists this CVE so far.
Requires: network access · Does not require: authentication, user interaction, special target conditions
Not enough data to detail.
Not enough data to detail.
Does not require: authentication, user interaction, special target conditions.
Not enough data to detail.
Confidentiality: highIntegrity: noneAvailability: none
The “Requires/Does not require” line and the confidentiality, integrity and availability impact come from the official CVSS vector. Method, applicability and mitigation are an automatic summary of the NVD description, public exploitation sources (Metasploit, Nuclei, Exploit-DB) and the CVE record via CIRCL (advisories and fixed version), linked under “References and technical detail”. Community reports come from CIRCL sightings and are unverified.