Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change
cve-program · CVE-2026-123872 · Published
No access to your tenant or devices. Every item links to its source. What this means
Historical advisory recorded 16 Nov 2026 23:26:07 UTC. Read the latest advisory.
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.
Read the publisher's advisorySee how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
cve-program · CVE-2026-123872 · Published
cve-program · CVE-2026-123872 · Published
This historical link shows only this version and versions saved before it. Browse all advisory history.