{"affected":[{"defaultStatus":"unaffected","product":"node","source":"CNA: openjs","vendor":"nodejs","versions":[{"lessThan":"22.23.5","status":"affected","version":"0.0.0","versionType":"semver"},{"lessThan":"24.22.3","status":"affected","version":"23.0.0","versionType":"semver"},{"lessThan":"26.13.1","status":"affected","version":"25.0.0","versionType":"semver"}]}],"cveId":"CVE-2026-123872","cwes":["CWE-287"],"description":"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.","epss":null,"exploits":[],"kev":null,"metrics":[{"score":8.1,"severity":"high","source":"CNA: openjs","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.0"}],"modifiedAt":1794421825193,"publishedAt":1794421825193,"references":[{"source":"CNA: openjs","tags":["vendor-advisory"],"url":"https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"},{"source":"CNA: openjs","tags":[],"url":"https://cna.openjsf.org/security-advisories.html"}],"remediation":[],"revision":"cdc68af8093afdd17e1934cb9f6d6e9afc7643f22508027719661dcfdfeb001a","sources":[{"modifiedAt":1794421825193,"name":"CNA: openjs","retrievedAt":1794424117278,"url":"https://www.cve.org/CVERecord?id=CVE-2026-123872"}],"ssvc":null,"status":"published","title":"Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change","updatedAt":1794424117278}