Koffei

CVE-2026-123866

🟡 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)
7.5
CVSS (v3.0, CVE List)
7.5
EPSS (2026-11-18)
0.551%
46.82th 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:H/I:N/A:N, EPSS: not yet scored (CWE-416: HTTP/2 stream teardown use-after-free can send freed response memory to the peer)

Fix

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

Official description

A use-after-free in Node.js HTTP/2 stream teardown can leak response memory, including the contents of other connections' response buffers, to a peer. When a stream is torn down while a write is still backpressured, for example by a peer RST_STREAM or by the server's own per-stream timeout destroying the stream, the stream's response buffer is freed but a reference to it is still used, so freed or unrelated heap memory is written to the socket instead of the intended response. On Node.js 26.x and 24.x the teardown can be driven purely by a remote peer once the window-size change from 26.9.0 and 24.22.0 is present, and on all supported lines the same defect is reachable through an application-initiated teardown such as a per-stream idle timeout. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

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

CWE-416