All reports
Medium

nodejs: nodejs: Certificate validation bypass via TLS session cache reuse

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-123877

Probability of exploitation in the next 30 days: 0.24%

FIRST EPSS · 2026-11-19

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.

A flaw was found in Node.js. When managing outbound HTTPS connections, the client connection agent generates identical session-cache keys for requests with differing Certificate Authority (CA) trust configurations. Consequently, an existing Transport Layer Security (TLS) session established under a broad trust policy can be improperly reused by a subsequent request requiring stricter validation. An attacker could exploit this certificate validation bypass to receive confidential data that the application inadvertently transmits to an unauthorized server.