Koffei

CVE-2026-106072

🟡 Low

node · 22.x <= 22.23.3, 24.x <= 24.22.0, 26.x <= 26.12.0

CVSS (Koffei note)
6.7
CVSS (v3.0, CVE List)
6.7
EPSS (2026-11-18)
0.617%
50.30th percentile

Exploitation

No — no exploitation mentioned by the vendor or CERT-FR; no SSVC yet; not in KEV. Not in the 0day "In the Wild" sheet (checked 18/11/2026). cyberveille RSS: checked 18/11/2026 (feed 19/10 to 17/11/2026), no result (automated enrichment)

Timeline

  1. 23/10/2026CVE record published (CVE List)
  2. 18/11/2026CERT-FR relays Oracle's off-cycle November update for six product lines

Risk

6.7 Medium (v3.0, CNA (hackerone)) — AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L, EPSS 0.617%, 50.18th percentile, scored 2026-11-17 (CWE-295: tls.checkServerIdentity() normalizes non-canonical IPv4 spellings (e.g. 0177.0.0.1, 127.1) and matches them as DNS names, so a cert with a numeric DNS SAN but no IP SAN can authenticate an IP endpoint.)

Fix

Yes — Oracle PeopleSoft: Oracle cspunov2026 (17/11/2026)

Official description

A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client connects using a non-canonical IPv4 spelling, such as `0177.0.0.1`, `0x7f.0.0.1`, `2130706433` or `127.1`. `tls.checkServerIdentity()` did not classify these hosts as IP addresses, but normalized them to their canonical form and matched the result against the certificate DNS names. A certificate containing `DNS:127.0.0.1` and no `IP Address:127.0.0.1` SAN was therefore accepted, while the same certificate is correctly rejected for `127.0.0.1`. Exploitation requires a certificate with a numeric DNS SAN issued by a CA trusted by the client, and a platform resolver that accepts these spellings, such as glibc. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

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

CWE-295