Skip to main content
VulnerabilityPublished

CVE-2026-123867: nodejs node · Improper Certificate Validation

Affects nodejs nodeSource CVE Database V5

0
Compare

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

Data as of 11 Nov 2026, 18:48 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 nodejs 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

This vulnerability is fixed in Node.js versions 22.23.5, 24.22.3, and 26.13.1. Users should upgrade affected Node.js versions to these fixed releases to remediate the issue. No other mitigation or workaround is indicated in the vendor advisory.

Description

CVE-2026-123867 is a vulnerability in Node.js versions 22.x, 24.x, and 26.x that allows a client authorized for the default hostname to bypass mutual TLS (mTLS) authorization and access a protected hostname it is not authorized for. This occurs due to improper certificate validation when a TLS server assigns a hostname a different client-certificate CA without a server certificate in that SNI context, causing the server to fall back to the default client CA. As a result, a client with a certificate trusted by the default CA can complete mTLS to the protected hostname and read its response, even when requestCert and rejectUnauthorized are enabled. The issue is fixed in Node.js versions 22.23.5, 24.22.3, and 26.13.1.

References

Community reviews

Loading reviews…