Skip to main content
Mallory
HighVulnerability

CVE-2026-123864: Unauthenticated cross-connection memory disclosure in Node.js HTTPS

Published Nov 11, 2026 · Updated today
Trending this week#49of 427,813 vulnerabilities
Mention activity · 30 days30 mentions · peak 16 in a dayToday
CVSS8.1High · v3
EPSS0.36%31st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-123864CWE-416 · Use After Free

CVE-2026-123864 is a re-entrancy vulnerability in the HTTPS implementation of Node.js 22.x before 22.23.5, 24.x before 24.22.3, and 26.x before 26.13.1. TLSWrap::DoWrite() directly invokes ClearOut() for zero-byte writes. When JavaScript issues such a write inside the HTTP parser's on_body callback, ClearOut() can decrypt another TLS record while request-body parsing remains active, re-entering llhttp_execute(). This causes a use-after-free and an out-of-bounds heap read, allowing freed or unrelated heap memory to be processed as request-body data and disclosed through application responses or storage. Cleartext node:http is unaffected.

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.

An unauthenticated network client can obtain heap memory belonging to other connections in the same Node.js process. Potentially exposed information includes TLS private keys and other users' request data, compromising confidentiality across connections. Leaked bytes may also contaminate stored request bodies or associated logs. Exposure depends on application-handler behavior and the availability of an attacker-readable request-body echo or storage route; disclosure of any particular secret is not guaranteed.

Mitigation

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

No supported workaround is identified. Pending patching, restrict access to affected HTTPS listeners and isolate services to reduce exposure; these are interim risk reductions, not validated substitutes for the fix. Review handlers for early res.flushHeaders() calls followed by res.end() with non-empty data, and identify attacker-readable routes that echo or store request bodies. Cleartext node:http does not execute the vulnerable path, but disabling transport encryption is not an appropriate mitigation.

Remediation

Patch, then assume compromise.

Upgrade to Node.js 22.23.5, 24.22.3, or 26.13.1, or a later patched release in the corresponding supported branch. Alternatively, install the applicable distribution security update containing the fix. Rebuild and redeploy affected container images, restart Node.js processes, and verify the running runtime version. The fix prevents empty writes from causing nested TLS/parser execution and protects parser-buffer state. Migrate unsupported release lines to a supported patched version. Separately assess whether potentially exposed TLS keys, credentials, or session material require rotation or revocation; updating does not invalidate previously disclosed secrets.

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-123864 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-123864 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-123864?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-123864.
Is there a patch for CVE-2026-123864?
Upgrade to Node.js 22.23.5, 24.22.3, or 26.13.1, or a later patched release in the corresponding supported branch. Alternatively, install the applicable distribution security update containing the fix.
How severe is CVE-2026-123864?
CVE-2026-123864 has a CVSS v3 score of 8.1 (High) and an EPSS score of 0.36% (31st percentile) as of Nov 16, 2026.
Activity feed

Recent activity

30 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 SecurityAn unauthenticated HTTPS memory-disclosure vulnerability in Node.js, rated CVSS 8.1. Early response-header flushing followed by a nonempty response-ending write can cause parser re-entrancy and stale-buffer reads. Routes that echo or store request bodies can expose heap contents, including other connections’ data and TLS private keys. Affects 22.x, 24.x and 26.x; plain node:http servers are unaffected. Fixed in 22.23.5, 24.22.3 and 26.13.1. No supported workaround is provided; listener restrictions, isolation and pausing affected handler patterns are suggested only as unvalidated risk reduction.Read more ↗mkd cirtNews · Nov 12, 2026Node.js поправи 16 ранливости, вклучувајќи HTTP/2-пропусти што можат да предизвикаат пад на серверите и истекување податоци од други конекции | MKD-CIRT | Национален центар за одговор на компјутерски инцидентиHigh-severity memory-disclosure vulnerability in Node.js HTTPS servers affecting branches 22.x, 24.x and 26.x. An unauthenticated client may obtain other connections' memory, including TLS private keys and user requests. Exploitation requires a handler that calls res.flushHeaders() before the complete request body arrives and later calls res.end() with data, plus a route that returns or stores request bodies to retrieve the leaked data. Plain node:http servers are unaffected. Fixed in 22.23.5, 24.22.3 and 26.13.1; the advisory provides no guidance on rotating potentially exposed secrets.Read more ↗the hacker newsNews · Nov 12, 2026Node.js Fixes 16 Flaws, Including HTTP/2 Bugs That Crash Servers and Leak Other Connections' DataAn HTTPS memory-disclosure vulnerability affects Node.js 22.x, 24.x, and 26.x. It requires a handler that calls res.flushHeaders() before receiving the complete request body and later calls res.end() with data. Retrieving leaked memory also requires a route that returns or stores a request body. Plain node:http servers are unaffected. Fixed releases are 22.23.5, 24.22.3, and 26.13.1; the advisory provides no guidance on replacing potentially exposed secrets.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 ↗
+13 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 activity10Community discussion across Reddit, Mastodon, and other social sources.