vm2 versions 3.11.0 through 3.11.6 leak absolute host filesystem paths to sandboxed code through error stack formatting. Attacker-supplied code can force the host-realm source transformer to throw a SyntaxError (for example by calling eval with malformed source) and then read the error's .stack property; the bridge forwards the .stack read to the host-realm formatter, bypassing the sandbox-side host-path redaction introduced for GHSA-v27g-jcqj-v8rw. The returned stack string discloses absolute paths from vm2, Node.js internals, and the embedding application's own source tree, along with host function names. Default new VM() and new NodeVM() configurations are affected without any special options, and the issue persists when string eval is disabled because the host-side transformer throws before eval is handled. The impact is information disclosure only; no code execution results. Fixed in vm2 3.11.7.
CVE-2026-92936
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.8 from GitHub Security Advisory (severity: MODERATE) published 2026-10-05. A secondary CVSS source baseline 5.8; sources differ by 0.0.
Also known asEUVD-2026-81586 (ENISA EUVD) · GHSA-63m2-qqch-jxv2 (GitHub Security Advisories) · GHSA-x6m4-chr9-cg97 (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
- 5.8
- EG Score
- 5.8MEDIUMhigh confidence
- EG Risk
- 57EG Risk 57/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)Severity58% × 45%Impact severity (EG Severity): CVSS 5.8 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 or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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.5%
- EPSS %ILE
- 39th
- 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 (5.8): severity, escalated by confirmed exploitation. This CVE's 5.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.5% 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 or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 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 or medium mission impact; Attend at high (mission-essential systems).
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 partial (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)14 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 partial (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 17, 2026
Last Modified
September 17, 2026
Advisory Details (2)
Auto-updated Sep 17, 2026vm2 3.11.0 before 3.11.7 Information Disclosure via Error Stack | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vm2-3.11.0-before-3.11.7-information-disclosure-via-error-stackvm2 leaks absolute host filesystem paths to sandbox code via error stack formatting · Advisory · patriksimek/vm2 · GitHub
https://github.com/patriksimek/vm2/security/advisories/GHSA-x6m4-chr9-cg97Vendor Advisories for CVE-2026-92936(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| npm | vm2 @ 3.11.7 (fixes >= 3.11.0, <= 3.11.6) | — | ghsa |
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.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| vm2 | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 49× 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.
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. 1 repeat row among the latest 95 is merged into the row it repeats.
- 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-11-01 07:37 UTCGHSA enrichmentGHSA-x6m4-chr9-cg97 · GitHub severity MODERATE · GitHub CVSS 5.8
- 2026-11-01 07:37 UTCEG score recompute
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-28 02:55 UTCOSV refresh
- 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-25 13:50 UTCEG score recompute
- 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-18 02:59 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-17 15:35 UTCEG score recompute
- 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.5% · 37th percentile
Show 69 moreShow fewer
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-12 14:44 UTCEG score recompute
- 2026-10-11 19:13 UTCEG score recompute
- 2026-10-11 16:29 UTCEG score recompute
- 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-11 13:43 UTCEG score recompute
- 2026-10-11 09:04 UTCEG score recompute
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-10 08:13 UTCEG score recompute
- 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-09 07:35 UTCEG score recompute
- 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-08 06:56 UTCEG score recompute
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-07 06:19 UTCEG score recompute
- 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-06 05:41 UTCEG score recompute
- 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-05 05:05 UTCEG score recompute
- 2026-10-05 05:05 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-04 04:27 UTCEG score recompute
- 2026-10-04 04:27 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-10-03 03:50 UTCEG score recompute
- 2026-10-03 03:50 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-10-02 03:11 UTCEG score recompute
- 2026-10-02 03:11 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-01 02:07 UTCEG score recompute
- 2026-10-01 02:07 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-09-30 01:29 UTCEG score recompute
- 2026-09-30 01:29 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-29 00:52 UTCEG score recompute
- 2026-09-29 00:52 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 36th percentile
- 2026-09-28 00:15 UTCEG score recompute
- 2026-09-28 00:15 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.5% · 36th percentile
- 2026-09-26 23:38 UTCEG score recompute
- 2026-09-26 23:38 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 36th percentile
- 2026-09-25 23:00 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-24 22:19 UTCEG score recompute
- 2026-09-24 22:19 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 36th percentile
- 2026-09-23 21:41 UTCEG score recompute
- 2026-09-23 21:41 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-22 21:04 UTCEG score recompute
- 2026-09-22 21:04 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-21 20:27 UTCEG score recompute
- 2026-09-21 20:27 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-20 19:50 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-19 19:13 UTCEG score recompute
- 2026-09-19 19:13 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-18 18:36 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-17 17:58 UTCEG score recompute
- 2026-09-17 17:58 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-17 15:54 UTCEG score recompute
- 2026-09-17 15:54 UTCGHSA enrichmentGHSA-63m2-qqch-jxv2 · GitHub CVSS 5.8
- 2026-09-17 14:23 UTCEG score recompute
- 2026-09-17 13:51 UTCEG score recomputeFirst assessed: 5.8 MEDIUM
- 2026-09-17 13:49 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownnpm:vm2
- CVE-2026-100723NVD 7.5EG 10.0CRITICAL
- CVE-2026-100721NVD 9.0EG 10.0CRITICAL
- CVE-2026-93605EG 10.0CRITICAL
- CVE-2026-92960EG 10.0CRITICAL
- CVE-2026-92956EG 10.0CRITICAL
- CVE-2026-92955EG 10.0CRITICAL
- CVE-2026-92953EG 10.0CRITICAL
- CVE-2026-92947EG 10.0CRITICAL
- CVE-2026-92946EG 10.0CRITICAL
- CVE-2026-92941EG 10.0CRITICAL
Frequently asked(5)
What is CVE-2026-92936?
When was CVE-2026-92936 made public?
Is CVE-2026-92936 actively exploited?
What is the CVSS score of CVE-2026-92936?
How do I remediate CVE-2026-92936?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-92936
Is Your Infrastructure Affected by CVE-2026-92936?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.