Koffei

CVE-2026-106070

🟡 Low

node · 26.x <=26.12.0

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

3.7 Low (v3.0, CNA (hackerone)) — AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N, EPSS 0.367%, 31.01th percentile, scored 2026-11-17 (CWE-840: zlib.ZipFile can return bytes not belonging to the requested entry when local and central headers mismatch, and CRC still passes, so a Node.js scanner may approve content different from what other ZIP tools extract.)

Fix

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

Official description

A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails. When `zipEntry.modified` is read on an archive whose local header does not match its central directory, either directly or while compacting the archive, the validation error is caught but the parsed local header is left cached without a content offset. A later content read then returns attacker-controlled bytes from the start of the file instead of rejecting the archive, and CRC-32 verification still passes because the attacker controls the central directory CRC. A Node.js-based scanner can therefore approve different content from what another ZIP implementation extracts from the same archive. This vulnerability affects Node.js **26.x**.

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

CWE-840