CVE-2026-106074

A flaw was found in Node.js crypto. Internal entropy caches used by crypto.randomUUID(), crypto.randomUUIDv7(), and crypto.randomInt() can be saved into user-land startup snapshots (--build-snapshot) and single executable applications built with useSnapshot. If those APIs (or dependents such as URL.createObjectURL()) run while the snapshot is built, every process started from that snapshot can replay the same initial values until the cache is refilled (on the order of 127 UUIDs and about 1,000 randomInt values). Identifiers expected to be unique may collide across processes, and values from one process may be predictable to an observer of another process started from the same snapshot.

This is a Moderate severity flaw. Red Hat rates it Moderate because impact is limited to confidentiality and integrity of early pseudo-random values (Low/Low) and exploitation requires building or distributing a startup snapshot or SEA with useSnapshot after exercising the affected APIs (high attack complexity; non-default deployment pattern). Typical Red Hat Node.js RPM and service deployments that do not ship custom snapshots are less exposed in practice, but the vulnerable code is present in affected Node.js streams. OS-level hardening does not reset Node/V8 entropy caches across snapshot restore.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.

Do not ship or run user-land snapshots or SEAs built with useSnapshot if crypto.randomUUID/randomInt (or APIs that use them) executed during snapshot creation. Prefer generating security-sensitive nonces and identifiers after process start, outside snapshot initialization.