Skip to main content
Mallory
HighVulnerability

CVE-2026-123874: Use-after-free in Node.js HTTP/2 file-serving streams

Published Nov 11, 2026 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days16 mentions · peak 11 in a dayToday
CVSS7.5High · v3
EPSS0.55%47th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-123874CWE-416 · Use After Free

CVE-2026-123874 is a use-after-free vulnerability in Node.js HTTP/2 file serving, affecting versions 24.22.0 through 24.22.2 and 26.9.0 through 26.13.0. When an application uses stream.respondWithFile() or stream.respondWithFD(), an unauthenticated client can reset a stream while a socket write referencing its Http2Stream object remains queued. The stream can be freed before the write completes, after which the completion code dereferences the freed object and makes a virtual call through it. The vulnerability permits server memory corruption over either TLS or cleartext HTTP/2 connections.

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.

Remote, unauthenticated exploitation can corrupt server process memory and cause denial of service. The vulnerability is rated High with a CVSS v3 base score of 7.5, reflecting high availability impact. Although the invalid access includes a virtual call through a freed object, arbitrary code execution and confidentiality compromise have not been demonstrated.

Mitigation

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

No vendor-supported workaround is identified. Pending an upgrade, reduce exposure by restricting access to affected HTTP/2 listeners or terminating HTTP/2 at a reverse proxy that communicates with Node.js exclusively over HTTP/1.1. Ensure alternate listeners do not expose the affected HTTP/2 file-serving functionality. These measures are interim exposure reductions, not substitutes for patching.

Remediation

Patch, then assume compromise.

Upgrade Node.js 24.x to version 24.22.3 or later, or Node.js 26.x to version 26.13.1 or later. The fix retains HTTP/2 streams while socket writes remain pending. Apply the corresponding distribution security update where applicable, rebuild and redeploy affected container images, restart running workloads, and verify the active runtime version.

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-123874 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-123874 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-123874?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-123874.
Is there a patch for CVE-2026-123874?
Upgrade Node.js 24.x to version 24.22.3 or later, or Node.js 26.x to version 26.13.1 or later. The fix retains HTTP/2 streams while socket writes remain pending.
How severe is CVE-2026-123874?
CVE-2026-123874 has a CVSS v3 score of 7.5 (High) and an EPSS score of 0.55% (47th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
phoenix security blogNews · Nov 12, 2026Node.js Vulnerabilities: TLS Key Leak and HTTP/2 Crash - Phoenix SecurityA High-rated use-after-free vulnerability in Node.js HTTP/2 file-serving streams. Resetting a stream during a pending write can cause a virtual call through a freed object. The advisory does not claim demonstrated code execution. Patches are available in the security release; restricting access, isolating affected services or removing unnecessary native HTTP/2 exposure is suggested only as unvalidated interim risk reduction.Read more ↗mkd cirtNews · Nov 12, 2026Node.js поправи 16 ранливости, вклучувајќи HTTP/2-пропусти што можат да предизвикаат пад на серверите и истекување податоци од други конекции | MKD-CIRT | Национален центар за одговор на компјутерски инцидентиHigh-severity memory-corruption vulnerability affecting Node.js HTTP/2 servers in branches 24.x and 26.x when serving files through stream.respondWithFile() or stream.respondWithFD(). A client can corrupt server memory. Fixed in 24.22.3 and 26.13.1.Read more ↗the hacker newsNews · Nov 12, 2026Node.js Fixes 16 Flaws, Including HTTP/2 Bugs That Crash Servers and Leak Other Connections' DataA high-severity memory-corruption vulnerability affects Node.js 24.x and 26.x HTTP/2 servers serving files through stream.respondWithFile() or stream.respondWithFD(). Fixed releases are 24.22.3 and 26.13.1. The content does not establish remote code execution.Read more ↗tenable cloud security pluginsNews · Nov 12, 2026Alpine: nodejs: security update to 24.22.3-r0 | Tenable®Unknown. The advisory includes this CVE in the Node.js package update but provides no vulnerability-specific description.Read more ↗
+8 more in the timeline. Sign up to see them
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 activity1Community discussion across Reddit, Mastodon, and other social sources.