CVE-2026-93606

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” 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.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-82901 (ENISA EUVD) · GHSA-q84h-7qfg-c6j8 (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG 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
54th
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-11-12). 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 Nov 7, 2026
🔬 Proof of concept available. Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Sandbox 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-m6jw
Web page

vm2 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-species

Patch Availability(6)

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 21× in last 7d / 92× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 343 rows 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 243 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  2. 2026-11-13 05:11 UTCEchelonGraph re-scored
  3. 2026-11-13 05:11 UTCVendor advisory
  4. 2026-11-13 05:11 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  5. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  6. 2026-11-12 05:37 UTCEchelonGraph re-scored
  7. 2026-11-12 05:37 UTCVendor advisory
  8. 2026-11-12 05:37 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  9. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  10. 2026-11-11 06:03 UTCEchelonGraph re-scored
  11. 2026-11-11 06:03 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  12. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-11-10 06:29 UTCEchelonGraph re-scored
  14. 2026-11-10 06:29 UTCVendor advisory
  15. 2026-11-10 06:29 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  16. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-11-09 06:56 UTCEchelonGraph re-scored
  18. 2026-11-09 06:56 UTCVendor advisory
  19. 2026-11-09 06:56 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  20. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  21. 2026-11-08 07:22 UTCEchelonGraph re-scored
  22. 2026-11-08 07:22 UTCVendor advisory
  23. 2026-11-08 07:22 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  24. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  25. 2026-11-07 07:47 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-07 07:47 UTCVendor advisory
  2. 2026-11-07 07:47 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  3. 2026-11-06 22:25 UTCOSV refresh
  4. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-11-06 08:13 UTCEchelonGraph re-scored
  6. 2026-11-06 08:13 UTCVendor advisory
  7. 2026-11-06 08:13 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  8. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-11-05 08:39 UTCEchelonGraph re-scored
  10. 2026-11-05 08:39 UTCVendor advisory
  11. 2026-11-05 08:39 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  12. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-11-04 09:05 UTCEchelonGraph re-scored
  14. 2026-11-04 09:05 UTCVendor advisory
  15. 2026-11-04 09:05 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  16. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-11-03 09:31 UTCEchelonGraph re-scored
  18. 2026-11-03 09:31 UTCVendor advisory
  19. 2026-11-03 09:31 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  20. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  21. 2026-11-02 09:56 UTCEchelonGraph re-scored
  22. 2026-11-02 09:56 UTCVendor advisory
  23. 2026-11-02 09:56 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  24. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  25. 2026-11-01 10:22 UTCEchelonGraph re-scored
  26. 2026-11-01 10:22 UTCVendor advisory
  27. 2026-11-01 10:22 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  28. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  29. 2026-10-31 10:48 UTCEchelonGraph re-scored
  30. 2026-10-31 10:48 UTCVendor advisory
  31. 2026-10-31 10:48 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  32. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  33. 2026-10-30 11:14 UTCEchelonGraph re-scored
  34. 2026-10-30 11:14 UTCVendor advisory
  35. 2026-10-30 11:14 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  36. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  37. 2026-10-29 11:41 UTCEchelonGraph re-scored
  38. 2026-10-29 11:41 UTCVendor advisory
  39. 2026-10-29 11:41 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  40. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  41. 2026-10-28 12:06 UTCEchelonGraph re-scored
  42. 2026-10-28 12:06 UTCVendor advisory
  43. 2026-10-28 12:06 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  44. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  45. 2026-10-27 12:32 UTCEchelonGraph re-scored
  46. 2026-10-27 12:32 UTCVendor advisory
  47. 2026-10-27 12:32 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  48. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  49. 2026-10-26 12:58 UTCEchelonGraph re-scored
  50. 2026-10-26 12:58 UTCVendor advisory
  51. 2026-10-26 12:58 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  52. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  53. 2026-10-25 13:49 UTCEchelonGraph re-scored
  54. 2026-10-25 13:19 UTCEchelonGraph re-scored
  55. 2026-10-25 13:19 UTCVendor advisory
  56. 2026-10-25 13:19 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  57. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  58. 2026-10-24 13:44 UTCEchelonGraph re-scored
  59. 2026-10-24 13:44 UTCVendor advisory
  60. 2026-10-24 13:44 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  61. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  62. 2026-10-23 14:11 UTCEchelonGraph re-scored
  63. 2026-10-23 14:11 UTCVendor advisory
  64. 2026-10-23 14:11 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  65. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  66. 2026-10-22 14:36 UTCEchelonGraph re-scored
  67. 2026-10-22 14:36 UTCVendor advisory
  68. 2026-10-22 14:36 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  69. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  70. 2026-10-21 14:38 UTCEchelonGraph re-scored
  71. 2026-10-21 14:38 UTCVendor advisory
  72. 2026-10-21 14:38 UTCGHSA enrichmentGHSA-q84h-7qfg-c6j8 · GitHub severity CRITICAL · GitHub CVSS 10.0
  73. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  74. 2026-10-20 15:03 UTCEchelonGraph re-scored
  75. 2026-10-20 15:03 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-93606?
CVE-2026-93606 is a critical-severity vulnerability; its CVE record was published on September 18, 2026. 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…
When was CVE-2026-93606 made public?
CVE-2026-93606 was made public on September 3, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 18, 2026. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-93606 actively exploited?
CVE-2026-93606 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93606?
CVE-2026-93606 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93606?
A fix for CVE-2026-93606 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-93606 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-93606

Explore →

Is Your Infrastructure Affected by CVE-2026-93606?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.