Skip to main content
Mallory
MediumVulnerability

CVE-2026-123867: Per-host mutual-TLS authorization bypass in Node.js

Published Nov 11, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days15 mentions · peak 7 in a dayToday
CVSS4.2Medium · v3.1
EPSS0.15%4th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-123867CWE-863

CVE-2026-123867 is a hostname-specific mutual-TLS authorization bypass affecting Node.js 22.x, 24.x, and 26.x. When server.addContext() configures an SNI context with a distinct client-certificate CA but no server certificate, setSniContext returns false. CertCbDone consequently skips installing the hostname-specific CA and silently retains the default client CA. A client trusted by the default CA, but not by the protected hostname's CA, can complete mutual TLS and read the protected hostname's response even with requestCert and rejectUnauthorized enabled.

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.

The vulnerability breaks hostname-specific client-certificate authorization boundaries, allowing clients trusted only by the default CA to access protected responses. Unauthorized operations may also be possible where the application relies on that mutual-TLS boundary for authorization. Conversely, legitimate clients trusted only by the protected hostname's CA can be rejected because the server applies the wrong trust policy.

Mitigation

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

Until patched, avoid CA-only SNI contexts for hostname-specific mutual TLS. Configure each protected SNI context with a server certificate and corresponding private key in addition to its intended client CA, and verify that clients trusted only by the default CA are rejected. Alternatively, isolate different client-CA policies on separate TLS listeners rather than relying on CA-only SNI overrides.

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 branch. The fix applies the client-CA configuration of SNI contexts even when they contain no server certificate. Distribution-managed installations should use the applicable vendor security update; Alpine fixes include 22.23.5-r0 and 24.22.3-r0. Patch availability varies by distribution.

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-123867 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-123867 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-123867?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-123867.
Is there a patch for CVE-2026-123867?
Upgrade to Node.js 22.23.5, 24.22.3, or 26.13.1, or a later patched release in the corresponding branch. The fix applies the client-CA configuration of SNI contexts even when they contain no server certificate.
How severe is CVE-2026-123867?
CVE-2026-123867 has a CVSS v3.1 score of 4.2 (Medium) and an EPSS score of 0.15% (4th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

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

View more in app →
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 ↗tenable cloud security pluginsNews · Nov 12, 2026Alpine: nodejs: security update to 22.23.5-r0 | Tenable®Referenced as a vulnerability covered by the Alpine nodejs security update. No vulnerability-specific technical details are provided. The prescribed update is nodejs and related packages version 22.23.5-r0 or later.Read more ↗tenable nessus pluginsNews · Nov 12, 2026Linux Distros Unpatched Vulnerability : CVE-2026-123867 | Tenable®A mutual-TLS authorization bypass in Node.js occurs when a hostname-specific SNI context specifies a client-certificate CA but no server certificate. Node.js fails to install that context's client CA and instead retains the default CA. A client trusted by the default CA can access the protected hostname despite requestCert and rejectUnauthorized being enabled. The advisory assigns a CVSS v3 base score of 4.2 and reports no vendor-supplied patch or known solution.Read more ↗tenable nessus pluginsNews · Nov 12, 2026Amazon Linux 2023 : nodejs24, nodejs24-devel, nodejs24-full-i1... | Tenable®A CA-only SNI context configured through server.addContext() does not install its intended client-certificate CA when it lacks a server certificate. The default CA remains active, allowing a client trusted by the default CA to access a protected hostname despite requestCert and rejectUnauthorized being enabled. Node.js 26.x, 24.x, and 22.x are affected.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 activityCommunity discussion across Reddit, Mastodon, and other social sources.