CVE-2026-123875
🟡 LowNode.js (node) · < 22.23.5 ; 23.0.0 to < 24.22.3 ; 25.0.0 to < 26.13.1 (record); EOL 20.x and 25.x unpatched
CVSS (Koffei note)
5.9CVSS (v3.0, CVE List)
5.9EPSS (2026-11-18)
0.461%40.64th percentile
Exploitation
No — the Node.js advisory and The Hacker News report no exploitation and no public PoC; not in CISA KEV (mirror current to 10/11/2026); record has no CISA ADP block yet. Sploitus not checked. No dated incident was read for this row. Daily CyberNews corroboration: 2026-11-12 Cybersecurity Watch (EDIT 0001).
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
5.9 Medium (v3.0, OpenJS CNA) — AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, EPSS: not yet scored (CWE-476: cancelling a
respondWithFile() download causes a NULL dereference that crashes the server)Fix
Yes — Node.js 22.23.5 / 24.22.3 / 26.13.1 (11/11/2026) (advisory)
Official description
A NULL pointer dereference in Node.js HTTP/2 lets an unauthenticated client crash the server, over both TLS and cleartext, by cancelling file downloads. When the server serves a file with stream.respondWithFile() or stream.respondWithFD() and the client cancels the request, a StreamPipe used for the transfer is torn down in an order that leaves a NULL pointer which is then dereferenced, aborting the process. No crafted frames are needed, and a handful of cancelled requests against a default file-serving handler is enough. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE-476