Skip to main content
CVE-2026-123867VulnerabilityPublished

Node.js lets a client authorized · Per-host Mutual-TLS Authorization Bypass

Source GCVE Database

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

Not known to be exploited · CVSS 4.2 Medium · fixed in 26.13.1 : update node when convenient.

Data as of 11 Nov 2026, 22:35 UTC

CVSS 3.0 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.04.2
Patch
Available – fixed in 26.13.1, 24.22.3, 22.23.5
CVSS:3.0/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 11 Nov 2026.

What to do

Upgrade node to 26.13.1, 24.22.3 or 22.23.5.

Affected software

ProductAffectedFixed in
nodejsnodeAffected
  • >=25.0.0 <26.13.1
Fixed in
  • 26.13.1
nodejsnodeAffected
  • >=23.0.0 <24.22.3
Fixed in
  • 24.22.3
nodejsnodeAffected
  • <22.23.5
Fixed in
  • 22.23.5

AI-suggested

Users should monitor Node.js vendor advisories for updates addressing this issue. If you cannot patch yet, consider avoiding configurations that assign client-certificate CAs to hostnames without corresponding server certificates. Review TLS server configurations to ensure each SNI context includes a valid server certificate to prevent fallback to the default client CA.

Description

A vulnerability in Node.js allows a client authorized for the default hostname to bypass per-host mutual TLS (mTLS) authorization and access a protected hostname it is not authorized for. This occurs when a TLS server configures a hostname with a client-certificate CA but no server certificate, causing the client CA to fall back to the default. As a result, a client trusted by the default CA can complete mTLS to the protected hostname despite lacking proper authorization. This affects Node.js versions 22.x, 24.x, and 26.x.

References

Community reviews

Loading reviews…