CVE-2026-123867
Last modified
CVE-2026-123867 is a medium-severity vulnerability rated 4.2/10 on the CVSS scale. A per-host mutual-TLS authorization bypass in Node.js lets a client authorized for the default hostname reach a protected hostname it is not authorized for. When a TLS server assigns a hostname a different client-certificate CA with `server.addContext(host, { ca: protectedCA })` but no server certificate in that SNI context, the per-host client CA is never installed and the handshake falls back to the default client CA. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
A per-host mutual-TLS authorization bypass in Node.js lets a client authorized for the default hostname reach a protected hostname it is not authorized for. When a TLS server assigns a hostname a different client-certificate CA with `server.addContext(host, { ca: protectedCA })` but no server certificate in that SNI context, the per-host client CA is never installed and the handshake falls back to the default client CA. In `src/crypto/crypto_tls.cc`, `CertCbDone` installs the SNI context's CA only when `setSniContext` succeeds, but `setSniContext` returns `false` for a context with no server certificate, so a CA-only SNI context silently keeps the default CA. A client holding a certificate trusted by the default CA, but not the protected CA, can therefore complete mTLS to the protected hostname and read its response even with `requestCert` and `rejectUnauthorized` enabled, while a client certified by the protected CA is rejected. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| nodejs | node | >= 0.0.0, < 22.23.5; >= 23.0.0, < 24.22.3; >= 25.0.0, < 26.13.1 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-123867?
How severe is CVE-2026-123867?
How do I fix CVE-2026-123867?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-123861Authorization Bypass Through User-Controlled Key vulnerabili…5.3
- CVE-2026-123862An uncatchable exception in the Node.js zlib streaming API l…2.9
- CVE-2026-123863A reachable assertion in Node.js HTTP/2 session teardown let…8.2
- CVE-2026-123864A re-entrancy flaw in Node.js HTTPS lets an unauthenticated …8.1
- CVE-2026-123865An unauthenticated HTTP/2 client can permanently leak Node.j…7.5
- CVE-2026-123866A use-after-free in Node.js HTTP/2 stream teardown can leak …7.5
- CVE-2026-123868An unauthenticated HTTP/2 client can exhaust Node.js server …5.9
- CVE-2026-12387Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel D…5.1
- CVE-2026-123870The otterdog webapp evaluates a format-string built from the…9.5
- CVE-2026-123871Node.js discloses proxy credentials in ERR_PROXY_INVALID_CON…6.2
- CVE-2026-123872A client certificate authentication bypass in Node.js TLS le…8.1
- CVE-2026-123874A use-after-free in Node.js HTTP/2 lets an unauthenticated c…7.5
Are you affected by CVE-2026-123867?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
