11 matches found
DEBIAN-CVE-2026-123874
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...
ALPINE-CVE-2026-123874
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...
CVE-2026-123874
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...
CVE-2026-123875
Node.js versions 26.x, 24.x, and 22.x are vulnerable to a NULL pointer dereference within the HTTP/2 implementation. The flaw occurs when a client cancels a request for a file being served via stream.respondWithFile() or stream.respondWithFD() . This cancellation causes a StreamPipe to be torn do...
EUVD-2026-123701
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...
CVE-2026-123874 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...
CVE-2026-123874
A use-after-free vulnerability in Node.js HTTP/2 allows an unauthenticated client to corrupt server memory over both TLS and cleartext. The issue occurs when the server serves files using respondWithFile() or respondWithFD(); a client can trigger the server to free an Http2Stream while a write re...
CVE-2026-123874
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...
CVE-2026-123874
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...
CVE-2026-123874: nodejs node: A use-after-free in Node.js HTTP/2 lets an unauthenticated client corrupt server memory, over both TLS and cleartext,…
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...
PT-2026-145422
Name of the Vulnerable Software and Affected Versions Node.js versions 26.9.0 through 26.x Node.js versions 24.22.0 through 24.22.2 Description A use-after-free issue in the HTTP/2 implementation allows an unauthenticated client to corrupt server memory over TLS or cleartext. This occurs when the...