{"answers":{"affected":"2 open source packages ship an affected version, including node and node-min.","exploited":"There is no known exploitation of CVE-2026-106074 in the wild and no public exploit code.","fix":"Upgrade node to a fixed version for your release line: 22.23.4, 24.22.1 or 26.12.1.","what":"CVE-2026-106074 is a medium-severity vulnerability in nodejs node, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-106074 and fix it if it is affected.\n\nWhat it is: CVE-2026-106074 is a medium-severity vulnerability in nodejs node, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-106074 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node (Bitnami): affected all versions; fixed in 22.23.4, 24.22.1, 26.12.1\n- node-min (Bitnami): affected all versions; fixed in 22.23.4, 24.22.1, 26.12.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-106074/ (Markdown: https://insights.sbomify.com/CVE-2026-106074/index.md)","id":"CVE-2026-106074","markdown":"https://insights.sbomify.com/CVE-2026-106074/index.md","name":"CVE-2026-106074","record":{"aliases":["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"],"analysis":null,"analysis_generated_by":null,"assigner":"hackerone","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"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`.\n\nIf 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.\n\nThis vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":"2026-10-23","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-23T23:48:04Z","kind":"github_poc","ref":"https://github.com/CompleteTech-Security/node-cve-2026-106074-check","stars":0,"title":"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."}],"tier":"poc_unverified"},"has_fix":true,"headline":"A flaw in Node.js `crypto` causes the internal entropy caches used by `crypto.randomUUID()`, `crypto.randomUUIDv7()`, and `crypto.randomInt(","id":"CVE-2026-106074","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"A vulnerability allowing an authenticated organization-transfer peer to inject SQL into the configuration database of the source Veeam Backu","id":"CVE-2026-106076"},"packages":[{"ecosystem":"Bitnami","fixed":["22.23.4","24.22.1","26.12.1"],"introduced":["0","23.0.0","25.0.0"],"last_affected":[],"package":"node","purl":"pkg:bitnami/node","source":"BIT-node-2026-106074"},{"ecosystem":"Bitnami","fixed":["22.23.4","24.22.1","26.12.1"],"introduced":["0","23.0.0","25.0.0"],"last_affected":[],"package":"node-min","purl":"pkg:bitnami/node-min","source":"BIT-node-min-2026-106074"}],"prev":{"headline":"A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync()` without the required read permission checks.","id":"CVE-2026-106073"},"products":["node"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-23","vendors":["nodejs"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-106074/"}