Koffei

CVE-2026-123872

🟡 Low

Node.js (node) · < 22.23.5 ; 23.0.0 to < 24.22.3 ; 25.0.0 to < 26.13.1 (record); EOL 20.x and 25.x unpatched

CVSS (Koffei note)
8.1
CVSS (v3.0, CVE List)
8.1
EPSS (2026-11-18)
0.409%
35.88th percentile

Exploitation

No — the Node.js advisory and The Hacker News report no exploitation and no public PoC; not in CISA KEV (mirror current to 10/11/2026); record has no CISA ADP block yet. Sploitus not checked. No dated incident was read for this row. Daily CyberNews corroboration: 2026-11-12 Cybersecurity Watch (EDIT 0001).

Timeline

  1. 11/11/2026CVE record published (CVE List)
  2. 12/11/2026Node.js November security releases fix 16 flaws, seven high-severity, mostly in HTTP/2 and TLS server code

Risk

8.1 High (v3.0, OpenJS CNA) — AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, EPSS: not yet scored (CWE-287: TLS 1.2 renegotiation lets a client change servername and bypass per-host client-certificate authentication)

Fix

Yes — Node.js 22.23.5 / 24.22.3 / 26.13.1 (11/11/2026) (advisory)

Official 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.

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

CWE-287