Skip to main content
CVE-2026-123867VulnerabilityPublished Updated

Nodejs: A per-host mutual-TLS authorization bypass

Affects nodejsSource GCVE Database

0
Compare
Authoritative record:CVE-2026-123867· Medium 4.2

Not known to be exploited · CVSS 4.2 Medium.

Data as of 13 Nov 2026, 22:04 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (openjs)CVSS 3.14.2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10nodejspkg:deb/ubuntu/nodejs?arch=source&distro=stonkingOther threatsAffected
  • 22.22.1+dfsg+~cs22.19.15-1ubuntu1 – 24.19.0+dfsg+~cs24.13.3-1ubuntu1
4 affected builds
Fixed in–
Ubuntu 26.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=resoluteOther threatsAffected
  • 20.19.4+dfsg-1 – 22.22.1+dfsg+~cs22.19.15-1ubuntu1
6 affected builds
Fixed in–
Ubuntu 24.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=nobleOther threatsAffected
  • 18.13.0+dfsg1-1ubuntu2 – 18.19.1+dfsg-6ubuntu5
5 affected builds
Fixed in–
Ubuntu Pro 22.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/jammyOther threatsAffected
  • 12.22.5~dfsg-5ubuntu1 – 12.22.9~dfsg-1ubuntu3.6+esm2
12 affected builds
Fixed in–
Ubuntu Pro 20.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/focalOther threatsAffected
  • 10.15.2~dfsg-2ubuntu1 – 10.19.0~dfsg-3ubuntu1.6+esm2
10 affected builds
Fixed in–
Ubuntu Pro 18.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/bionicOther threatsAffected
  • 6.11.4~dfsg-1ubuntu1 – 8.10.0~dfsg-2ubuntu0.4+esm6
15 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…