CVE-2026-123874
🟡 LowNode.js (node) · 24.0.0 to < 24.22.3 ; 25.0.0 to < 26.13.1 (record; the description says 24.x since 24.22.0 and 26.x since 26.9.0)
46.62th percentile
Exploitation
Timeline
- 11/11/2026CVE record published (CVE List)
- 12/11/2026Node.js November security releases fix 16 flaws, seven high-severity, mostly in HTTP/2 and TLS server code
Risk
respondWithFile() stream is reset during a pending write)Fix
Official description
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).
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE-416