Node.js lets a client authorized · Per-host Mutual-TLS Authorization Bypass
Source GCVE Database
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
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 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
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.