A use-after-free in Node.js HTTP/2 lets an...
High severity
Unreviewed
Published
Nov 11, 2026
to the GitHub Advisory Database
•
Updated Nov 11, 2026
Description
Published by the National Vulnerability Database
Nov 11, 2026
Published to the GitHub Advisory Database
Nov 11, 2026
Last updated
Nov 11, 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).
References