Koffei

CVE-2026-123868

🟡 Low

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

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

5.9 Medium (v3.0, OpenJS CNA) — AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, EPSS: not yet scored (CWE-400: inbound HTTP/2 data queued on undrained streams is not counted against maxSessionMemory)

Fix

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

Official description

An unauthenticated HTTP/2 client can exhaust Node.js server memory because inbound DATA queued on an undrained stream is charged to no session budget. Each inbound DATA frame creates one JavaScript Buffer view in the receiving stream's readable queue, but nothing charges that queue to current_session_memory_: the socket read buffer is accounted only during parsing and released immediately, so whatever stays queued is accounted to nothing. A peer that fills a stream's receive window with one-byte DATA frames pays about 10 wire bytes per frame while the server retains about 114 bytes per frame, so a single stream on one connection can retain hundreds of megabytes from tens of megabytes sent. maxSessionMemory neither bounds the growth nor refuses new streams, because Http2Session::CanAddStream gates admission on the same counter that never sees the queue. This vulnerability affects Node.js 26.x and 24.x.

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

CWE-400