CVE-2026-123872

EUVD-2026-123699
A client certificate authentication bypass in Node.js TLS lets a client change the servername during TLS 1.2 renegotiation to reach endpoints it was not authorized for. On a server that applies different client-certificate policies per hostname, for example stricter admin-only client-cert auth on one host and ordinary client-cert auth on another, a client that authenticates for a permitted host can renegotiate the TLS 1.2 connection under a different servername and carry its existing authentication to the protected host, bypassing the stricter policy. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
ProviderTypeBase ScoreAtk. VectorAtk. ComplexityPriv. RequiredVector
openjsCNA
8.1 HIGH
NETWORK
LOW
LOW
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Base Score
CVSS 3.x
EPSS Score
Percentile: Unknown
Early Detection
Affected products identified ahead of NVD analysis through intelligence sources (CNA/ADP records, vendor advisories, Enginsight analysis).
VendorProductVersionSource
nodejsnode.js
0.0.0 ≤
𝑥
< 22.23.5
CNA
nodejsnode.js
23.0.0 ≤
𝑥
< 24.22.3
CNA
nodejsnode.js
25.0.0 ≤
𝑥
< 26.13.1
CNA