Node: Use of Insufficiently Random Values (CVE-2026-106074)
Published Last modified Sources: pwn.watch, Fortinet PSIRT, BSI, HKCERT, Msrc Update Guide, CVE.org
What is affected, what to do
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.
Update Node.js to version 22.23.4.
- Affected
- Node
lte 22.23.3..22.23.3 - Node
lte 24.22.0..24.22.0 - Node
lte 26.12.0..26.12.0
- Node
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
9.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
4.8
CVSS v3
Severity Medium on the scale from 0 to 10.
Source: pwn.watch, Fortinet PSIRT, BSI, HKCERT, Msrc Update Guide, CVE.org
0.3 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 24.7
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 58.88 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 9.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 4.8
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.3 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 24.7
- Elevated — this CVE ranks above at least 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-330
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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**.
Source: pwn.watch, fortinet_rss, BSI WID Portal, BSI CSAF, HKCERT (CC BY 3.0 HK) · HKCERT rating: high, Microsoft Security Update Guide, NVD (NIST), cvelistv5, CVE.org (MITRE)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| nodejs | node |
|
|
| Open Source | Node.js |
|
|
Vendors and products
Weakness classes (CWE)
CWE-330Use of Insufficiently Random Values
Class
The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.
Entry at MITRE CWE-330
References & sources
- nodejs.orgWednesday, October 21, 2026 Security Releasespwn-watch
- pwn.watchpwn.watch: Node2Shell / HTTP2Shell: Brotli RCE (CVE-2026-111497) in Node.js, Python, Envoy and Istio + Node.js October releasespwn-watch
- opensourcemalware.comPython Packages Vulnerable to Node2Shellpwn-watch
- thehackernews.comResearchers Demonstrate Node2Shell RCE Exploit on Node.js Build Using Crafted Brotli Datapwn-watch
- NVD (NIST)CVE-2026-111497 (NVD)pwn-watch
- nodejs.orgNode.js 26.12.1 (Current)pwn-watch
- vercel.comVercel bulletin: Brotli decoder RCEpwn-watch
- imperva.comNode2Shell: From Brotli Data to Remote Code Executionpwn-watch
- aikido.devNode2Shell: Node.js Brotli vulnerability allows remote code execution (CVE-2026-111497)pwn-watch
- github.comOut-of-Bounds Write in Brotli Decompressor (GHSA-3wvj-j6qm-62mr)pwn-watch
- patchtheplanet.orgBrotli vulnerability (CVE-2026-111497)pwn-watch
- aikido.devNode2Shell evolves to HTTP2Shell. Brotli flaw (CVE-2026-111497) blast radius affects many libraries & apps using HTTPs.pwn-watch
- news.ycombinator.comEvolving Threat: http2shell is an RCE in node, Python, and more (discussion)pwn-watch
- Microsoft Security Update GuideGoogle: CVE-2026-111497 Buffer overflow vulnerability in the Brotli decoderpwn-watch
- securityweek.comNode2Shell: Brotli Flaw Triggers Patching Across Microsoft, Node.js, Python Packagespwn-watch
- php.netUpdated PHP Windows builds for Brotli security fixpwn-watch
- bleepingcomputer.comMicrosoft releases emergency .NET patches for critical Brotli flawpwn-watch
- bleepingcomputer.comCritical 'HTTP2Shell' Brotli vulnerability triggers emergency patchespwn-watch
- theregister.comMicrosoft releases emergency .NET security fixes for Google Brotli bugpwn-watch
- cisa.govCISA Adds Two Known Exploited Vulnerabilities to Catalogpwn-watch
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
ReceivedHackerOne
CVSS V3: AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Weakness type: CWE-330
Description added or changed
Show 5 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —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**.CVSS added —AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:NWeakness type (CWE) added —CWE-330Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/106xxx/CVE-2026-106074.json">CVE-2026-106074</a>Reference added —https://nodejs.org/en/blog/vulnerability/october-2026-security-releasesSource identifier: support@hackerone.com
Linked advisories
- Multiple Node.js CVEsFortinet PSIRT
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-106074"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-106074.svg?lang=en" alt="CVE-2026-106074 – NEOSEC Intel" height="20"></a>