NetSight
high8.1

CVE-2026-123872

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 author…

Impact

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.

An attacker can exploit this over the network, with a regular user account, without any action by a user. If it succeeds: high risk of data being read, high risk of data or systems being changed.

Affected products · Node.js

ProductAffected versions
Node
from 0.0.0 before 22.23.5
from 23.0.0 before 24.22.3
from 25.0.0 before 26.13.1

Weakness classification

References