Skip to main content
Mallory
MediumVulnerability

CVE-2026-123875: Node.js HTTP/2 File-Download Cancellation NULL Pointer Dereference

Published Nov 11, 2026 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.9Medium · v3
EPSS0.46%41st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-123875CWE-476 · NULL Pointer Dereference

CVE-2026-123875 is a NULL pointer dereference in the Node.js HTTP/2 implementation affecting the 22.x, 24.x, and 26.x release lines. When a client cancels a file download served through stream.respondWithFile() or stream.respondWithFD(), incorrect StreamPipe teardown ordering leaves a NULL write-request pointer that is subsequently dereferenced, aborting the Node.js process. An unauthenticated remote client can trigger the issue over TLS-encrypted or cleartext HTTP/2 without crafted protocol frames.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation terminates the Node.js server process, interrupting active connections and making applications hosted by that process unavailable until it restarts. Repeated triggering can cause recurring service disruption. No confidentiality or integrity impact is identified. The vulnerability is rated Medium with a CVSS v3.0 base score of 5.9.

Mitigation

If you can’t patch tonight, do this now.

No vendor-supported workaround is specified. As an interim risk-reduction measure, avoid serving files through stream.respondWithFile() or stream.respondWithFD() over HTTP/2, or temporarily disable HTTP/2 on affected file-serving endpoints. These measures remove the identified triggering path but do not replace upgrading.

Remediation

Patch, then assume compromise.

Upgrade to Node.js 22.23.5, 24.22.3, or 26.13.1, according to the deployed release line, or a later patched release. The fix guards against a NULL write request on a cancelled HTTP/2 stream. Distribution-managed installations should apply the corresponding vendor security update; Alpine Linux fixes include 22.23.5-r0 and 24.22.3-r0.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-123875 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-123875 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-123875?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-123875.
Is there a patch for CVE-2026-123875?
Upgrade to Node.js 22.23.5, 24.22.3, or 26.13.1, according to the deployed release line, or a later patched release. The fix guards against a NULL write request on a cancelled HTTP/2 stream.
How severe is CVE-2026-123875?
CVE-2026-123875 has a CVSS v3 score of 5.9 (Medium) and an EPSS score of 0.46% (41st percentile) as of Nov 16, 2026.
Activity feed

Recent activity

14 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.