# CVE-2026-106074: A flaw in Node.js `crypto` causes the internal entropy caches used by `crypto.randomUUID()`, `crypto.randomUUIDv7()`, and `crypto.randomInt(


- **Severity:** Medium 4.8 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** ALPINE-CVE-2026-106074, AZL-111050, BIT-node-2026-106074, BIT-node-min-2026-106074, DEBIAN-CVE-2026-106074, GHSA-w3gx-6c8w-v66f, UBUNTU-CVE-2026-106074

## What is CVE-2026-106074?

CVE-2026-106074 is a medium-severity vulnerability in nodejs node, published on 23 Oct 2026. 

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

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2026-106074?

2 open source packages ship an affected version, including node and node-min.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | All versions | 22.23.4, 24.22.1, 26.12.1 |
| `node-min` | Bitnami | All versions | 22.23.4, 24.22.1, 26.12.1 |

## How do I fix CVE-2026-106074?

Upgrade node to a fixed version for your release line: 22.23.4, 24.22.1 or 26.12.1.

## Is CVE-2026-106074 being exploited?

There is no known exploitation of CVE-2026-106074 in the wild and no public exploit code.

Public exploit code:

- Offline Node.js evidence checker for CVE-2026-106074: Crypto entropy cache duplication in snapshots. Single-file Python; JSON/CSV/HTML reports; no exploit payloads. (github_poc): https://github.com/CompleteTech-Security/node-cve-2026-106074-check

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-106074 and fix it if it is affected.

What it is: CVE-2026-106074 is a medium-severity vulnerability in nodejs node, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-106074 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected all versions; fixed in 22.23.4, 24.22.1, 26.12.1
- node-min (Bitnami): affected all versions; fixed in 22.23.4, 24.22.1, 26.12.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-106074/ (Markdown: https://insights.sbomify.com/CVE-2026-106074/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-106074
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-106074
- OSV: https://osv.dev/vulnerability/CVE-2026-106074

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-106074/
Summaries are generated and may contain mistakes; the official description above is the record.