Servers and applications
CVE-2026-123872
Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change
- Severity
- High 8.1
- Published
- 11 Nov 2026
- Last changed
- 11 Nov 2026
- Added to UpHeron
- 11 Nov 2026
- Fixed in
- 22.23.5, 24.22.3, 26.13.1
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data · Change data
- CVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N- Sources
- CVE Program
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.
Affected software
| Software | Affected versions |
|---|---|
Node.jsServers and applications · cna:nodejs|node |
|
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-123872