Koffei

CVE-2026-123863

🟡 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)
8.2
CVSS (v3.0, CVE List)
8.2
EPSS (2026-11-18)
0.516%
44.60th 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.2 High (v3.0, OpenJS CNA) — AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H, EPSS: not yet scored (CWE-617 reachable assertion: HTTP/2 session teardown assertion in ~Http2Session() lets an unauthenticated client abort the process)

Fix

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

Official description

A reachable assertion in Node.js HTTP/2 session teardown lets any unauthenticated client abort the server, over both TLS and cleartext. A client can arrange for an Http2Stream that still holds nghttp2-allocated header buffers to outlive its session: the stream is removed from the session's stream set but never detached, so when ~Http2Session() runs the memory accounting is nonzero and the CHECK_EQ(current_nghttp2_memory_, 0) assertion fails, terminating the process. The trigger needs only a default http2 server whose handler responds before the request body has ended, which is typical. It is a variant of CVE-2024-27983 that the earlier fix did not cover, because that fix only detached streams still tracked in the session. 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:L/A:H

CWE-617