Node.js up to 22.23.2/24.21.0/26.11.0 Crypto random values

Summaryinfo

A vulnerability labeled as problematic has been found in Node.js up to 22.23.2/24.21.0/26.11.0. Impacted is the function crypto.randomUUID/crypto.randomUUIDv7/crypto.randomInt of the component Crypto. Such manipulation leads to random values. This vulnerability is uniquely identified as CVE-2026-106074. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Node.js up to 22.23.2/24.21.0/26.11.0 and classified as problematic. Affected by this issue is the function crypto.randomUUID/crypto.randomUUIDv7/crypto.randomInt of the component Crypto. The manipulation with an unknown input leads to a random values vulnerability. Using CWE to declare the problem leads to CWE-330. The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers. Impacted is confidentiality. CVE summarizes:

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**.

The advisory is available at nodejs.org. This vulnerability is handled as CVE-2026-106074 since 10/06/2026. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1600.001 by the MITRE ATT&CK project.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• JavaScript Library

Name

• Node.js

Version

• 22.23.0
• 22.23.1
• 22.23.2
• 24.0
• 24.1
• 24.2
• 24.3
• 24.4
• 24.5
• 24.6
• 24.7
• 24.8
• 24.9
• 24.10
• 24.11
• 24.12
• 24.13
• 24.14
• 24.15
• 24.16
• 24.17
• 24.18
• 24.19
• 24.20
• 24.21.0
• 26.0
• 26.1
• 26.2
• 26.3
• 26.4
• 26.5
• 26.6
• 26.7
• 26.8
• 26.9
• 26.10
• 26.11.0

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion