Certificate Validation Bypass
Source GCVE Database
Not known to be exploited · CVSS 6.8 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 | 6.8 |
|---|
- 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:H/I:H/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
|
npmnodepkg:npm/nodeOther threats | Affected
| Fixed in
|
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, avoid relying on TLS session resumption when using different CA policies in Node.js https.Agent or explicitly manage session caches to prevent reuse across differing CA configurations.
Description
A certificate validation bypass vulnerability exists in Node.js https.Agent where cached TLS sessions authenticated under a broader CA policy can be reused in connections with stricter CA policies. This occurs because the session cache key does not differentiate between omitted and empty CA arrays, allowing a TLS 1.3 session authenticated with the default trust store to be resumed in a connection that explicitly supplies an empty CA list. This leads to unauthorized acceptance of TLS sessions and potential exposure of confidential data. The issue affects Node.js versions 22.x, 24.x, and 26.x.