CVE-2026-92942

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

vm2 before 3.11.7 (affected versions <= 3.11.6) does not enforce the VM({ timeout }) option on code executed outside the synchronous VM#run() call. The timeout only wraps the single call to _runScript() via doWithTimeout() in lib/vm.js, and FinalizationRegistry and WeakRef are exposed to sandboxed code unmodified (they are not among the hardened globals in lib/setup-sandbox.js). Sandboxed code can register a FinalizationRegistry cleanup callback against an object and then drop the only strong reference to it; vm.run() returns within the configured timeout, but when the V8 garbage collector later reclaims the object it invokes the sandboxed cleanup callback outside any vm2 timeout accounting. A busy loop in that callback blocks the host event loop for an unbounded period, resulting in denial of service. The time of invocation depends on the garbage collector (e.g. under memory pressure or with --expose-gc).

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
65
EG Risk 65/100CISA SSVC

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 computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Sep 17, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

vm2 before 3.11.7 Timeout Bypass via FinalizationRegistry | Advisories | VulnCheck

https://www.vulncheck.com/advisories/vm2-before-3.11.7-timeout-bypass-via-finalizationregistry
github Patch Available🟡 PoC Available

vm2: timeout Option Bypass via FinalizationRegistry Cleanup Callback (Unbounded Host Event-Loop Block) · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-r4fx-v8hh-22mv

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatansible-automation-platform/automation-portal:17902549632026-09-28redhat
redhatansible-automation-platform/automation-portal:17902564052026-09-28redhat

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 36× in last 7d / 80× 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.

  1. 2026-10-05 00:47 UTCEG score recompute
  2. 2026-10-05 00:47 UTCVendor advisory
  3. 2026-10-05 00:47 UTCGHSA enrichment
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 11:49 UTCVendor advisory
  6. 2026-10-04 11:49 UTCGHSA enrichment
  7. 2026-10-03 22:55 UTCEG score recompute
  8. 2026-10-03 22:55 UTCVendor advisory
  9. 2026-10-03 22:55 UTCGHSA enrichment
  10. 2026-10-03 10:00 UTCVendor advisory
  11. 2026-10-03 10:00 UTCGHSA enrichment
  12. 2026-10-02 20:53 UTCEG score recompute
  13. 2026-10-02 20:53 UTCVendor advisory
  14. 2026-10-02 20:53 UTCGHSA enrichment
  15. 2026-10-02 07:58 UTCEG score recompute
  16. 2026-10-02 07:58 UTCVendor advisory
  17. 2026-10-02 07:58 UTCGHSA enrichment
  18. 2026-10-01 19:51 UTCEPSS rescore
  19. 2026-10-01 19:03 UTCVendor advisory
  20. 2026-10-01 19:03 UTCGHSA enrichment
  21. 2026-10-01 06:08 UTCVendor advisory
  22. 2026-10-01 06:08 UTCGHSA enrichment
  23. 2026-09-30 17:12 UTCEG score recompute
  24. 2026-09-30 17:12 UTCVendor advisory
  25. 2026-09-30 17:12 UTCGHSA enrichment
Show 55 more
  1. 2026-09-30 15:04 UTCEPSS rescore
  2. 2026-09-30 04:17 UTCEG score recompute
  3. 2026-09-30 04:17 UTCVendor advisory
  4. 2026-09-30 04:17 UTCGHSA enrichment
  5. 2026-09-29 15:22 UTCVendor advisory
  6. 2026-09-29 15:22 UTCGHSA enrichment
  7. 2026-09-29 02:28 UTCEG score recompute
  8. 2026-09-29 02:28 UTCGHSA enrichment
  9. 2026-09-28 13:52 UTCEPSS rescore
  10. 2026-09-28 13:52 UTCEPSS rescore
  11. 2026-09-28 13:33 UTCGHSA enrichment
  12. 2026-09-28 00:38 UTCEG score recompute
  13. 2026-09-28 00:38 UTCGHSA enrichment
  14. 2026-09-27 13:49 UTCEPSS rescore
  15. 2026-09-27 11:43 UTCGHSA enrichment
  16. 2026-09-26 22:41 UTCEG score recompute
  17. 2026-09-26 22:41 UTCGHSA enrichment
  18. 2026-09-26 15:59 UTCEPSS rescore
  19. 2026-09-26 09:39 UTCEG score recompute
  20. 2026-09-26 09:38 UTCGHSA enrichment
  21. 2026-09-25 20:42 UTCGHSA enrichment
  22. 2026-09-25 07:44 UTCGHSA enrichment
  23. 2026-09-24 18:49 UTCEG score recompute
  24. 2026-09-24 18:49 UTCGHSA enrichment
  25. 2026-09-24 14:04 UTCEPSS rescore
  26. 2026-09-24 05:54 UTCEG score recompute
  27. 2026-09-24 05:54 UTCGHSA enrichment
  28. 2026-09-23 17:54 UTCEPSS rescore
  29. 2026-09-23 16:59 UTCGHSA enrichment
  30. 2026-09-23 04:05 UTCEG score recompute
  31. 2026-09-23 04:05 UTCGHSA enrichment
  32. 2026-09-22 16:01 UTCEPSS rescore
  33. 2026-09-22 15:08 UTCGHSA enrichment
  34. 2026-09-22 02:14 UTCEG score recompute
  35. 2026-09-22 02:14 UTCGHSA enrichment
  36. 2026-09-21 21:09 UTCEPSS rescore
  37. 2026-09-21 13:18 UTCGHSA enrichment
  38. 2026-09-21 00:23 UTCEG score recompute
  39. 2026-09-21 00:23 UTCGHSA enrichment
  40. 2026-09-20 20:16 UTCEPSS rescore
  41. 2026-09-20 11:26 UTCGHSA enrichment
  42. 2026-09-19 22:27 UTCEG score recompute
  43. 2026-09-19 22:27 UTCGHSA enrichment
  44. 2026-09-19 09:32 UTCGHSA enrichment
  45. 2026-09-18 20:35 UTCEG score recompute
  46. 2026-09-18 20:35 UTCGHSA enrichment
  47. 2026-09-18 19:44 UTCEG score recompute
  48. 2026-09-18 19:44 UTCGHSA enrichment
  49. 2026-09-18 19:28 UTCEPSS rescore
  50. 2026-09-18 16:12 UTCGHSA enrichment
  51. 2026-09-18 03:17 UTCEG score recompute
  52. 2026-09-18 03:17 UTCGHSA enrichment
  53. 2026-09-17 14:22 UTCEG score recompute
  54. 2026-09-17 13:50 UTCEG score recompute
  55. 2026-09-17 13:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92942?
CVE-2026-92942 is a high vulnerability published on September 17, 2026. vm2 before 3.11.7 (affected versions <= 3.11.6) does not enforce the VM({ timeout }) option on code executed outside the synchronous VM#run() call. The timeout only wraps the single call to _runScript() via doWithTimeout() in lib/vm.js, and FinalizationRegistry and WeakRef are exposed to sandboxed…
When was CVE-2026-92942 disclosed?
CVE-2026-92942 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92942 actively exploited?
CVE-2026-92942 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92942?
CVE-2026-92942 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92942?
A fix for CVE-2026-92942 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-92942 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-92942?

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