Koffei

CVE-2026-123871

🟡 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)
6.2
CVSS (v3.0, CVE List)
6.2
EPSS (2026-11-18)
0.173%
6.87th 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

6.2 Medium (v3.0, OpenJS CNA) — AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, EPSS: not yet scored (CWE-209: proxy credentials exposed in ERR_PROXY_INVALID_CONFIG error messages)

Fix

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

Official description

Node.js discloses proxy credentials in ERR_PROXY_INVALID_CONFIG error messages. CVE-2026-48615 established that a proxy credential must not appear in a Node.js error message and redacted the username and password from ProxyConfig.href, but that fix missed four error paths in the same subsystem, one of them inside the same constructor, which interpolate the raw proxy URL, credentials included, into an ERR_PROXY_INVALID_CONFIG message. The proxy URL comes from the environment, but the defect is the sink: a secret that Node.js redacts everywhere else is emitted verbatim into a much wider audience than the process environment, such as stderr, container logs, log aggregation, and crash reporting services. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

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

CWE-209