CVE-2026-106074: CWE-330 Use of Insufficiently Random Values in nodejs node
Description
A vulnerability in Node.js affects the internal entropy caches used by crypto functions such as crypto.randomUUID(), crypto.randomUUIDv7(), and crypto.randomInt() when user-land startup snapshots or single executable applications are built with useSnapshot. If these functions are called during snapshot creation, the cached random values are reused across processes started from that snapshot, causing collisions and predictability of supposedly unique identifiers. This impacts Node.js versions 22.23.3, 24.22.0, and 26.12.0.
CVSS v3.0
Score 4.8medium
Affected software
nodejs
node
pkg:npm/nodeRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-106074 is a vulnerability in Node.js where the internal entropy caches for crypto.randomUUID(), crypto.randomUUIDv7(), and crypto.randomInt() are saved into user-land startup snapshots (--build-snapshot) and single executable applications built with useSnapshot. When these functions or dependent APIs like URL.createObjectURL() are invoked during snapshot creation, the cached random values are reused in every process started from that snapshot until the cache is refilled. This results in up to 127 UUIDs and about 1,000 randomInt() values being identical across processes, leading to collisions of identifiers expected to be unique and predictability of values across processes. The affected versions are Node.js 22.23.3, 24.22.0, and 26.12.0.
Potential Impact
The vulnerability causes identifiers that should be unique, such as UUIDs and random integers generated by the affected crypto functions, to collide across processes spawned from the same snapshot. Additionally, values generated by one process can be predicted by observing another process, reducing randomness and potentially undermining security mechanisms relying on these values. The CVSS score is 4.8 (medium severity), indicating limited confidentiality and integrity impact with no availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid calling crypto.randomUUID(), crypto.randomUUIDv7(), crypto.randomInt(), or APIs relying on them during snapshot creation with --build-snapshot or useSnapshot. Consider rebuilding snapshots without invoking these functions or avoid using snapshots if possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2026-10-06T15:00:00.655Z
- Cvss Version
- 3.0
- State
- PUBLISHED
Threat ID: 6adb8965d73cc49347a5c6eb
Added to database: 10/23/2026, 16:20:53 UTC
Last enriched: 10/23/2026, 16:35:26 UTC
Last updated: 10/23/2026, 16:35:52 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.