Threat intelligence · CVEs & news
Published: 11/11/2026 · Modified: 11/16/2026
A use-after-free in Node.js HTTP/2 lets an unauthenticated client corrupt server memory, over both TLS and cleartext, when the server serves files with respondWithFile() or respondWithFD(). A client can make the server free an Http2Stream while a write request that points to it is still queued on the socket; when that write completes, the code dereferences and makes a virtual call through the freed object. The only precondition is that the application serves a file with stream.respondWithFile() or stream.respondWithFD(), with default settings otherwise. This vulnerability affects Node.js 26.x (since 26.9.0) and 24.x (since 24.22.0).
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: noneIntegrity: noneAvailability: high
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.