Nodejs: A certificate validation bypass
Affects nodejsSource GCVE Database
Not known to be exploited · CVSS 6.8 Medium.
Data as of 13 Nov 2026, 22:04 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.0 | 6.8 |
|---|
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 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10nodejspkg:deb/ubuntu/nodejs?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu Pro 22.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/jammyOther threats | Affected
| Fixed in– |
Ubuntu Pro 20.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/focalOther threats | Affected
| Fixed in– |
Ubuntu Pro 18.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
References
- ubuntu.com/security/CVE-2026-123877 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-123877 (opens in a new tab)
- nodejs.org/en/blog/vulnerability/november-2026-security-releases (opens in a new tab)
- cna.openjsf.org/security-advisories.html (opens in a new tab)
- nodejs.org/en/blog/vulnerability/november-2026-security-releases (opens in a new tab)