CVE-2026-123867: nodejs node · Improper Certificate Validation
Affects nodejs nodeSource CVE Database V5
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
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.0 | 4.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:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| nodejsnode | Affected
| Fixed in
|
| nodejsnode | Affected
| Fixed in
|
| nodejsnode | Affected
| Fixed in
|
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.