Koffei

CVE-2026-106074

🟡 Low

node · 22.23.3, 24.22.0, 26.12.0 (22.x, 24.x, 26.x lines)

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

4.8 Medium (v3.0, CNA (hackerone)) — AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N, EPSS 0.334%, 27.16th percentile, scored 2026-11-17 (CWE-330: Node.js crypto entropy caches for randomUUID/randomUUIDv7/randomInt are saved into user-land startup snapshots and SEA useSnapshot builds, so processes from one snapshot return identical, predictable values until the cache refills.)

Fix

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

Official description

A flaw in Node.js `crypto` causes the internal entropy caches used by `crypto.randomUUID()`, `crypto.randomUUIDv7()`, and `crypto.randomInt()` to be saved into user-land startup snapshots (`--build-snapshot`) and single executable applications built with `useSnapshot`. If any of these functions, or an API that relies on them such as `URL.createObjectURL()`, is called while the snapshot is built, every process started from that snapshot returns the same values until the cache is refilled: up to 127 UUIDs and about 1,000 `randomInt()` values. Identifiers expected to be unique can collide across processes, and values issued by one process can be predicted by observing another. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

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

CWE-330