Koffei

CVE-2026-126051

🟡 Low

Node.js (node) · 24.0.0 to < 24.22.3 ; 25.0.0 to < 26.13.1 (record)

CVSS (Koffei note)
7.5
CVSS (v3.0, CVE List)
7.5
EPSS (2026-11-18)
0.863%
59.30th 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

7.5 High (v3.0, OpenJS CNA) — AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, EPSS: not yet scored (CWE-476 in the record (the advisory calls it a use-after-destroy): a deferred TLS handshake callback crashes TLS servers using SNICallback, OCSPRequest, newSession/resumeSession hooks or server.addContext())

Fix

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

Official description

A deferred-callback use-after-destroy in Node.js TLS server handshake handling allows a remote, unauthenticated attacker to terminate the server process. When a TLS server uses any of the SNICallback, OCSPRequest, newSession, or resumeSession hooks, or server.addContext(), the corresponding OpenSSL callbacks are deferred, and the deferred code does not handle the underlying socket being destroyed between scheduling and execution. By sending a client hello that reaches the vulnerable path (for example, no SNI together with an OCSP request) followed by padding and a socket FIN, an attacker makes OpenSSL deliver the client hello and the end-of-file in the same tick, so the socket is destroyed before the deferred callback runs and the process raises an uncaught exception instead of emitting an 'error' event. This vulnerability affects Node.js 26.x and 24.x.

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

CWE-476