CVE-2026-123875 Null dereference in node
Unauthenticated clients can crash Node.js HTTP/2 servers serving files by cancelling file downloads.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Harmful if only installed
- No
- Needs a specific call
- Yes
- Fix
- Available
What is CVE-2026-123875?
CVE-2026-123875 is a medium-severity null pointer dereference vulnerability in nodejs node, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
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.
Weakness: CWE-476
Which versions are affected by CVE-2026-123875?
An affected version is only exploitable if your software calls respondWithFile(), stream.respondWithFile() or stream.respondWithFD(). Many projects that include it are not exposed.
How do I fix CVE-2026-123875?
No fix published yet.
Upgrade to the fixed version. Check every result that can be empty before using it. More about Null pointer dereference.
Is CVE-2026-123875 being exploited?
There is no known exploitation of CVE-2026-123875 in the wild and no public exploit code.
Sources
Also known as ALPINE-CVE-2026-123875, BELL-CVE-2026-123875, DEBIAN-CVE-2026-123875, GHSA-v6qh-ch8g-j833, UBUNTU-CVE-2026-123875.