Koffei

CVE-2026-123874

🟡 Low

Node.js (node) · 24.0.0 to < 24.22.3 ; 25.0.0 to < 26.13.1 (record; the description says 24.x since 24.22.0 and 26.x since 26.9.0)

CVSS (Koffei note)
7.5
CVSS (v3.0, CVE List)
7.5
EPSS (2026-11-18)
0.548%
46.62th 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-416: HTTP/2 use-after-free when a respondWithFile() stream is reset during a pending write)

Fix

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

Official description

A use-after-free in Node.js HTTP/2 lets an unauthenticated client corrupt server memory, over both TLS and cleartext, when the server serves files with respondWithFile() or respondWithFD(). A client can make the server free an Http2Stream while a write request that points to it is still queued on the socket; when that write completes, the code dereferences and makes a virtual call through the freed object. The only precondition is that the application serves a file with stream.respondWithFile() or stream.respondWithFD(), with default settings otherwise. This vulnerability affects Node.js 26.x (since 26.9.0) and 24.x (since 24.22.0).

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

CWE-416