vm2 before 3.11.8 does not fully enforce the allowAsync: false option in VM and NodeVM. While localPromise.prototype.then is replaced with a handler that throws 'Async not available', the sandbox's Promise static methods (Promise.resolve, Promise.all, Promise.race, Promise.any, and Promise.allSettled) still assimilate attacker-supplied thenables: native promise resolution performs PromiseResolveThenableJob and invokes the sandboxed code's then method in a microtask without passing through the patched then, so the async restriction is never applied. As a result, sandboxed script can schedule work that runs after VM.run() or NodeVM.run() has returned and outside the configured timeout, continuing to execute after the host believes execution is complete.
CVE-2026-92959
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. a secondary CVSS source baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(high)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
September 17, 2026
Last Modified
September 17, 2026
Advisory Details (2)
Auto-updated Sep 17, 2026vm2 before 3.11.8 allowAsync Bypass via Promise Thenable | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vm2-before-3.11.8-allowasync-bypass-via-promise-thenable`allowAsync: false` can be bypassed through Promise thenable assimilation in VM and NodeVM · Advisory · patriksimek/vm2 · GitHub
https://github.com/patriksimek/vm2/security/advisories/GHSA-f8gf-w286-fmq2Vendor Advisories for CVE-2026-92959(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-09-19 17:29 UTCEG score recompute
- 2026-09-19 17:29 UTCGHSA enrichment
- 2026-09-19 04:45 UTCEG score recompute
- 2026-09-19 04:44 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 15:59 UTCGHSA enrichment
- 2026-09-18 03:06 UTCEG score recompute
- 2026-09-18 03:06 UTCGHSA enrichment
- 2026-09-17 14:22 UTCEG score recompute
- 2026-09-17 13:50 UTCEG score recompute
- 2026-09-17 13:49 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-92959?
When was CVE-2026-92959 disclosed?
Is CVE-2026-92959 actively exploited?
What is the CVSS score of CVE-2026-92959?
How do I remediate CVE-2026-92959?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-92959
Is Your Infrastructure Affected by CVE-2026-92959?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.