Node
Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0.0.0, < 22.23.5
- >= 23.0.0, < 24.22.3
- >= 25.0.0, < 26.13.1
Fixed in 22.23.5, 24.22.3, 26.13.1
Mitigation
Upgrade node to 22.23.5 or 24.22.3 or 26.13.1 or later.
References
- Vendor advisory nodejs.org/en/blog/vulnerability/november-2026…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.