Threat intelligence · CVEs & news
Published: 11/11/2026 · Modified: 11/16/2026
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.
No confirmed-exploitation catalog lists this CVE so far.
Requires: network access, privileged account · Does not require: user interaction, special target conditions
Not enough data to detail.
Not enough data to detail.
Does not require: user interaction, special target conditions.
Not enough data to detail.
Confidentiality: highIntegrity: highAvailability: none
The “Requires/Does not require” line and the confidentiality, integrity and availability impact come from the official CVSS vector. Method, applicability and mitigation are an automatic summary of the NVD description, public exploitation sources (Metasploit, Nuclei, Exploit-DB) and the CVE record via CIRCL (advisories and fixed version), linked under “References and technical detail”. Community reports come from CIRCL sightings and are unverified.