Skip to main content
CVE-2026-123872VulnerabilityPublished

Client Certificate Authentication Bypass

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-123872· High 8.1

Not known to be exploited · CVSS 8.1 High · fixed in 26.13.1 : patch node soon.

Data as of 11 Nov 2026, 22:34 UTC

CVSS 3.0 base score
8.1High
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.08.1
Patch
Available – fixed in 26.13.1, 24.22.3, 22.23.5
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
npmnodepkg:npm/nodeOther threatsAffected
  • <22.23.5
  • >=23.0.0 <24.22.3
  • >=25.0.0 <26.13.1
Fixed in
  • 22.23.5
  • 24.22.3
  • 26.13.1

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

AI-suggested

If you cannot patch yet, administrators should consider disabling TLS 1.2 renegotiation or enforcing uniform client-certificate policies across hostnames to mitigate the risk.

Description

A vulnerability in Node.js TLS allows a client to bypass client certificate authentication by changing the servername during TLS 1.2 renegotiation. This enables a client authenticated for a less restrictive host to access endpoints with stricter client-certificate policies, effectively bypassing intended access controls. The issue affects Node.js versions 22.x, 24.x, and 26.x.

References

Community reviews

Loading reviews…