{"id":"EM-20261111-XEEQ","url":"https://cyber.eventmonitor.net/incident/EM-20261111-XEEQ/node-js-tls-vulnerability-cve-2026-123872/","type":"cve","title":"Node.js TLS Vulnerability (CVE-2026-123872)","subtitle":"CVE-2026-123872","subject":"CVE-2026-123872","status":"Developing","severity":"high","affected":[],"headline":null,"born":"2026-11-11T19:17:34.270Z","firstSignal":"2026-11-11T18:30:25.000Z","lastSignal":"2026-11-11T19:17:34.270Z","updated":"2026-11-12T00:31:06.720Z","revision":1,"life":[{"status":"Born","at":"2026-11-11T19:17:34.270Z","why":"second independent source: C6 NVD CVE API 2.0"},{"status":"Developing","at":"2026-11-11T19:17:34.270Z","why":"signals keep joining"}],"changeLog":[{"at":"2026-11-11T18:30:25.000Z","what":"First signal: C41 Red Hat Security Data"},{"at":"2026-11-11T19:17:34.270Z","what":"Born: second source, C6 NVD CVE API 2.0. Page EM-20261111-XEEQ created."}],"stages":[{"name":"Disclosed","at":"2026-11-11T19:17:34.270Z","detail":"C6 NVD published"},{"name":"Scored","at":"2026-11-11T19:17:34.270Z","detail":"CVSS 8.1"},{"name":"Exploited","at":null,"detail":"No exploitation reported"},{"name":"Advisories","at":null,"detail":"None yet"},{"name":"Vendor Response","at":"2026-11-11T18:30:25.000Z","detail":"C41 published"},{"name":"Resolved","at":null,"detail":"After 14 quiet days"}],"signals":[{"at":"2026-11-11T18:30:25.000Z","source":"C41","sourceName":"Red Hat Security Data","role":"Vendor","severity":3,"title":"Red Hat: CVE-2026-123872 (important)","text":"nodejs: Node.js: Client certificate authentication bypass via TLS renegotiation","url":"https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-123872.json"},{"at":"2026-11-11T19:17:34.270Z","source":"C6","sourceName":"NVD CVE API 2.0","role":"Database","severity":3,"title":"CVE-2026-123872 (CVSS 8.1)","text":"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…","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-123872"}],"crowd":[],"reference":{"nvd":{"published":"2026-11-11T19:17:34.270","score":8.1,"severity":"HIGH","desc":"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…","product":"","seen":1794435185345},"kev":null,"epss":null,"p0":false},"mergedInto":null,"publisher":"Event Monitor Cyber"}