A flaw in Node.js `crypto` causes the internal entropy...
Moderate severity
Unreviewed
Published
Oct 23, 2026
to the GitHub Advisory Database
•
Updated Oct 23, 2026
Description
Published by the National Vulnerability Database
Oct 23, 2026
Published to the GitHub Advisory Database
Oct 23, 2026
Last updated
Oct 23, 2026
A flaw in Node.js
cryptocauses the internal entropy caches used bycrypto.randomUUID(),crypto.randomUUIDv7(), andcrypto.randomInt()to be saved into user-land startup snapshots (--build-snapshot) and single executable applications built withuseSnapshot.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,000randomInt()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.
References