Skip to main content
← All vulnerabilities
CVE-2026-106074EUVD-2026-109104GHSA-W3GX-6C8W-V66F

A flaw in Node.js `crypto` causes the internal entropy caches used by `crypto.randomUUID()`, `crypto.randomUUIDv7()`, and `crypto.randomInt(

Published
Last modified
published
Not listed in CISA KEV
None on Exploit-DB, Metasploit or GitHub

Summary

Node.js applications that use the `crypto` module's `randomUUID()`, `randomUUIDv7()`, or `randomInt()` functions, including startup snapshots and single executable applications built with snapshots, are affected. Because cached random values can be saved into the snapshot and reused by every process started from it, generated IDs may collide across processes and random values may be predictable by an attacker who observes another process.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original 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.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • nodejs node

    From 22.23.3 · through 22.23.3; From 24.22.0 · through 24.22.0; From 26.12.0 · through 26.12.0

References 1

nodejs.org