CVE-2026-123867: Per-host mutual-TLS authorization bypass in Node.js
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.
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.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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.
Recent activity
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.