Node
Node.js is vulnerable to an HTTP/2 use-after-free via respondWithFile() stream reset during a pending write
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).
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 24.0.0, < 24.22.3
- >= 25.0.0, < 26.13.1
Fixed in 24.22.3, 26.13.1
Mitigation
Upgrade node to 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.