CVE-2026-123877
🟡 LowNode.js (node) · < 22.23.5 ; 23.0.0 to < 24.22.3 ; 25.0.0 to < 26.13.1 (record); EOL 20.x and 25.x unpatched
15.56th percentile
Exploitation
Timeline
- 11/11/2026CVE record published (CVE List)
- 12/11/2026Node.js November security releases fix 16 flaws, seven high-severity, mostly in HTTP/2 and TLS server code
Risk
https.Agent reuses TLS sessions across different CA policies, bypassing certificate validation)Fix
Official 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.
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
CWE-295