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**.
Fix
Microsoft's update · Moderate
- Release Notes — azl3 nodejs 24.21.0-1 on Azure Linux 3.0 · build 24.22.1-0
From the 2026-Oct release note of Microsoft's Security Update Guide, revised 2026-10-28.
Public exploits 2
- CompleTetech-Security/node-cve-2026-106074-check PoC on GitHub
- completetech-security/node-cve-2026-106074-check PoC on GitHub
Each line links to the index that lists it, never to exploit code. Exploit-DB's "verified" and a Metasploit rank of good or better count as verified; a PoC-in-GitHub entry is a repository's claim.
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 4
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-23 16:15
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-23 19:42
- StatusReceived → PublishedNVD modified 2026-10-23 16:15
- First seenCVSS 4.8NVD modified 2026-10-23 17:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.