nodejs · Node.js · published 2026-11-11
CVE-2026-123867Node.js is vulnerable to a per-host mTLS authorization bypass via a CA-only SNI context failing open to the default CA
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-123867 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 5% of all CVEs. This Node.js vulnerability: CVSS 4.2 (v3.1). Fixed upstream in Node.js 26.13.1, 24.22.3, 22.23.5; Debian, Ubuntu and Red Hat Enterprise Linux still have unfixed releases. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Node.js 26.13.1, 24.22.3, 22.23.5.
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | nodejs | No fix yet |
| 12 bookworm | nodejs | No fix yet | |
| Ubuntu | 26.04 LTS | nodejs | No fix yet |
| 24.04 LTS | nodejs | No fix yet | |
| Red Hat Enterprise Linux (+3 more packages) | RHEL 9 | nodejs | No fix yet |
| RHEL 8 | nodejs | No fix yet |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Language runtimeNode.js
Node.js security releases: 26.13.1, 24.22.3, 22.23.5
Upgrade to
26.13.124.22.322.23.5Why: Vendor security release for server software (most severe: CVE-2026-123863).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (5th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 4.2 (v3.1)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- nodejs node
0.0.0to before22.23.5(affected)23.0.0to before24.22.3(affected)25.0.0to before26.13.1(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.