vm2 (npm) versions 3.12.0 and earlier contain a sandbox escape in VM and NodeVM. When an embedder exposes a host API that returns a host-realm Promise, the bridge's rejection sanitizer (hostPromiseSanitizeReject / makeSanitizedPromiseCallback / normalizeHostPromiseCallbacks in lib/bridge.js) only wraps then/catch rejection slots that hold a function, and the sandbox-side Symbol.species/.then neutralization is installed only on the sandbox intrinsic Promise.prototype, so it never applies to a host Promise. Code running inside the sandbox can overwrite p.constructor[Symbol.species] on the host Promise and then call p.then() with no onRejected handler; V8 substitutes its internal Thrower, which re-throws the raw host rejection value into a resolve/reject closure captured by the attacker. This delivers an unsanitized, fully functional bridge proxy of the host object to sandboxed code, bypassing handleException and hostPromiseSanitizeReject. If the rejection value is host-pivotable (for example a host process object), this results in arbitrary code execution on the host. Fixed in 3.12.1.
CVE-2026-93606
“—” beside the score: it is equal to the CVSS score beside it.
Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-18. A secondary CVSS source baseline 10.0; sources differ by 0.0.
Also known asEUVD-2026-82901 (ENISA EUVD) · GHSA-q84h-7qfg-c6j8 (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 10.0
- EG Score
- 10.0CRITICALmedium confidence
- EG Risk
- 76EG Risk 76/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity100% × 45%Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.7%
- EPSS %ILE
- 53rd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.
- EG Severity
- 10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (2)
Auto-updated Oct 31, 2026Sandbox escape in `VM`/`NodeVM`: a host-realm Promise's rejection sanitizer is bypassed via `Symbol.species` hijack and a missing `onRejected` handler, delivering the raw host rejection value to the sandbox · Advisory · patriksimek/vm2 · GitHub
https://github.com/patriksimek/vm2/security/advisories/GHSA-6454-5x88-m6jwvm2 before 3.12.1 Sandbox Escape via Promise Symbol.species | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vm2-before-3.12.1-sandbox-escape-via-promise-symbol-speciesVendor Advisories for CVE-2026-93606(7)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:91651Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Developer Hub 1.9.10 release.
- RHSA-2026:82151Red Hat Product SecurityCritical
Red Hat Security Advisory: Ansible automation portal Red Hat Enterprise Linux Images
- RHSA-2026:80644Red Hat Product SecurityCritical
Red Hat Security Advisory: Ansible plug-ins for Red Hat Developer Hub Product Release Update
- RHSA-2026:80603Red Hat Product SecurityCritical
Red Hat Security Advisory: Ansible plug-ins for Red Hat Developer Hub Product Release Update
- RHSA-2026:79088Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Developer Hub 1.10.5 release.
- RHSA-2026:76788Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Developer Hub 1.10.5 Plugin Catalog GA plugins release.
- GHSA-q84h-7qfg-c6j8GitHub Security AdvisoriesCritical
vm2 (npm) versions 3.12.0 and earlier contain a sandbox escape in `VM` and `NodeVM`. When an...
Patch Availability(6)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | rhdh/rhdh-hub-rhel9:1793117813 | 2026-10-28 | redhat |
| redhat | ansible-automation-platform/bootc-automation-portal-rhel9:1791865660 | 2026-10-13 | redhat |
| redhat | ansible-automation-platform/automation-portal:1791295379 | 2026-10-12 | redhat |
| redhat | ansible-automation-platform/automation-portal:1791293780 | 2026-10-12 | redhat |
| redhat | rhdh/rhdh-hub-rhel9:1791311495 | 2026-10-08 | redhat |
| redhat | rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:1791251282 | 2026-10-06 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 28× in last 7d / 183× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 295 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 195 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-11-01 10:22 UTCEG score recompute
- 2026-11-01 10:22 UTCVendor advisory
- 2026-11-01 10:22 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-31 10:48 UTCEG score recompute
- 2026-10-31 10:48 UTCVendor advisory
- 2026-10-31 10:48 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-30 11:14 UTCEG score recompute
- 2026-10-30 11:14 UTCVendor advisory
- 2026-10-30 11:14 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-29 11:41 UTCEG score recompute
- 2026-10-29 11:41 UTCVendor advisory
- 2026-10-29 11:41 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-28 12:06 UTCEG score recompute
- 2026-10-28 12:06 UTCVendor advisory
- 2026-10-28 12:06 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-27 12:32 UTCEG score recompute
- 2026-10-27 12:32 UTCVendor advisory
- 2026-10-27 12:32 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
Show 75 moreShow fewer
- 2026-10-26 12:58 UTCEG score recompute
- 2026-10-26 12:58 UTCVendor advisory
- 2026-10-26 12:58 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-25 13:49 UTCEG score recompute
- 2026-10-25 13:19 UTCEG score recompute
- 2026-10-25 13:19 UTCVendor advisory
- 2026-10-25 13:19 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-24 13:44 UTCEG score recompute
- 2026-10-24 13:44 UTCVendor advisory
- 2026-10-24 13:44 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-23 14:11 UTCEG score recompute
- 2026-10-23 14:11 UTCVendor advisory
- 2026-10-23 14:11 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-22 14:36 UTCEG score recompute
- 2026-10-22 14:36 UTCVendor advisory
- 2026-10-22 14:36 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-21 14:38 UTCEG score recompute
- 2026-10-21 14:38 UTCVendor advisory
- 2026-10-21 14:38 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-20 15:03 UTCEG score recompute
- 2026-10-20 15:03 UTCVendor advisory
- 2026-10-20 15:02 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-19 15:10 UTCEG score recompute
- 2026-10-19 15:10 UTCVendor advisory
- 2026-10-19 15:10 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-18 15:35 UTCEG score recompute
- 2026-10-18 15:35 UTCVendor advisory
- 2026-10-18 15:35 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-18 06:13 UTCVendor advisory
- 2026-10-18 06:13 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-18 02:58 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-17 06:37 UTCEG score recompute
- 2026-10-17 06:37 UTCVendor advisory
- 2026-10-17 06:37 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-16 06:58 UTCEG score recompute
- 2026-10-16 06:58 UTCVendor advisory
- 2026-10-16 06:58 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-15 05:42 UTCEG score recompute
- 2026-10-15 05:42 UTCVendor advisory
- 2026-10-15 05:42 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-14 01:20 UTCEG score recompute
- 2026-10-14 01:20 UTCVendor advisory
- 2026-10-14 01:20 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-12 21:33 UTCEG score recompute
- 2026-10-12 21:33 UTCVendor advisory
- 2026-10-12 21:33 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-12 14:42 UTCEG score recompute
- 2026-10-12 04:57 UTCVendor advisory
- 2026-10-12 04:57 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 22:50 UTCVendor advisory
- 2026-10-11 22:50 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 19:12 UTCEG score recompute
- 2026-10-11 18:35 UTCVendor advisory
- 2026-10-11 18:35 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 16:28 UTCEG score recompute
- 2026-10-11 13:59 UTCEG score recompute
- 2026-10-11 13:59 UTCVendor advisory
- 2026-10-11 13:59 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-11 13:41 UTCEG score recompute
- 2026-10-11 08:23 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat:RHSA-2026:76788
Frequently asked(5)
What is CVE-2026-93606?
When was CVE-2026-93606 made public?
Is CVE-2026-93606 actively exploited?
What is the CVSS score of CVE-2026-93606?
How do I remediate CVE-2026-93606?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93606
Is Your Infrastructure Affected by CVE-2026-93606?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.