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).
CVE-2026-92942
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-05. A secondary CVSS source baseline 7.5; sources differ by 0.0.
Also known asEUVD-2026-81592 (ENISA EUVD) · GHSA-r4fx-v8hh-22mv (GitHub Security Advisories) · GHSA-vjcv-9j33-wj62 (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
- 7.5
- EG Score
- 7.5HIGHhigh confidence
- EG Risk
- 65EG Risk 65/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)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 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
- 42nd
- 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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-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 18, 2026
Advisory Details (2)
Auto-updated Sep 17, 2026vm2 before 3.11.7 Timeout Bypass via FinalizationRegistry | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vm2-before-3.11.7-timeout-bypass-via-finalizationregistryvm2: 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-22mvVendor Advisories for CVE-2026-92942(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: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-r4fx-v8hh-22mvGitHub Security AdvisoriesHigh
vm2: timeout Option Bypass via FinalizationRegistry Cleanup Callback (Unbounded Host Event-Loop Block)
- RHSA-2026:72722Red Hat Product SecurityHigh
Red Hat Security Advisory: Ansible plug-ins for Red Hat Developer Hub Product Release Update
- RHSA-2026:72712Red Hat Product SecurityHigh
Red Hat Security Advisory: Ansible plug-ins for Red Hat Developer Hub Product Release Update
Patch Availability(7)
| 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 | rhdh/rhdh-hub-rhel9:1791311495 | 2026-10-08 | redhat |
| redhat | rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:1791251282 | 2026-10-06 | redhat |
| redhat | ansible-automation-platform/automation-portal:1790254963 | 2026-09-28 | redhat |
| redhat | ansible-automation-platform/automation-portal:1790256405 | 2026-09-28 | redhat |
| npm | vm2 @ 3.11.7 (fixes <= 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 11× in last 7d / 74× 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 99 of 142 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 43 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.5% · 42nd percentile
- 2026-11-01 07:37 UTCGHSA enrichmentGHSA-r4fx-v8hh-22mv · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-01 07:37 UTCEG score recompute
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-31 07:15 UTCEG score recompute
- 2026-10-31 07:15 UTCVendor advisory
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-25 13:50 UTCEG score recompute
- 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-24 11:22 UTCEG score recompute
- 2026-10-24 11:22 UTCVendor advisory
- 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-18 02:59 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-17 15:35 UTCEG score recompute
Show 74 moreShow fewer
- 2026-10-17 15:35 UTCVendor advisory
- 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-13 04:31 UTCEG score recompute
- 2026-10-13 04:31 UTCVendor advisory
- 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-12 14:44 UTCEG score recompute
- 2026-10-11 19:12 UTCEG score recompute
- 2026-10-11 16:38 UTCVendor advisory
- 2026-10-11 16:29 UTCEG score recompute
- 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-11 13:43 UTCEG score recompute
- 2026-10-11 03:43 UTCEG score recompute
- 2026-10-11 03:43 UTCVendor advisory
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-10 11:18 UTCVendor advisory
- 2026-10-09 22:21 UTCEG score recompute
- 2026-10-09 22:21 UTCVendor advisory
- 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-09 09:26 UTCVendor advisory
- 2026-10-08 20:30 UTCEG score recompute
- 2026-10-08 20:30 UTCVendor advisory
- 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-08 07:04 UTCEG score recompute
- 2026-10-08 07:04 UTCVendor advisory
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-07 18:09 UTCVendor advisory
- 2026-10-07 04:38 UTCVendor advisory
- 2026-10-06 15:43 UTCEG score recompute
- 2026-10-06 15:43 UTCVendor advisory
- 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-06 02:39 UTCEG score recompute
- 2026-10-06 02:39 UTCVendor advisory
- 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-05 13:44 UTCVendor advisory
- 2026-10-05 13:44 UTCGHSA enrichmentGHSA-vjcv-9j33-wj62 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-05 00:47 UTCEG score recompute
- 2026-10-05 00:47 UTCVendor advisory
- 2026-10-05 00:47 UTCGHSA enrichmentGHSA-vjcv-9j33-wj62 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-04 11:49 UTCVendor advisory
- 2026-10-04 11:49 UTCGHSA enrichmentGHSA-vjcv-9j33-wj62 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-03 22:55 UTCEG score recompute
- 2026-10-03 22:55 UTCVendor advisory
- 2026-10-03 22:55 UTCGHSA enrichmentGHSA-vjcv-9j33-wj62 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-03 10:00 UTCVendor advisory
- 2026-10-03 10:00 UTCGHSA enrichmentGHSA-vjcv-9j33-wj62 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-02 20:53 UTCEG score recompute
- 2026-10-02 20:53 UTCVendor advisory
- 2026-10-02 20:53 UTCGHSA enrichmentGHSA-vjcv-9j33-wj62 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-02 07:58 UTCEG score recompute
- 2026-10-02 07:58 UTCVendor advisory
- 2026-10-02 07:58 UTCGHSA enrichmentGHSA-vjcv-9j33-wj62 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-01 19:03 UTCVendor advisory
- 2026-10-01 19:03 UTCGHSA enrichmentGHSA-vjcv-9j33-wj62 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-01 06:08 UTCVendor advisory
- 2026-10-01 06:08 UTCGHSA enrichmentGHSA-vjcv-9j33-wj62 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-30 17:12 UTCEG score recompute
- 2026-09-30 17:12 UTCVendor advisory
- 2026-09-30 17:12 UTCGHSA enrichmentGHSA-vjcv-9j33-wj62 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-30 04:17 UTCEG score recompute
- 2026-09-30 04:17 UTCVendor advisory
- 2026-09-30 04:17 UTCGHSA enrichmentGHSA-vjcv-9j33-wj62 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-29 15:22 UTCVendor advisory
- 2026-09-29 15:22 UTCGHSA enrichmentGHSA-vjcv-9j33-wj62 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-29 02:28 UTCEG score recompute
- 2026-09-29 02:28 UTCGHSA enrichmentGHSA-vjcv-9j33-wj62 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-28 13:33 UTCGHSA enrichmentGHSA-vjcv-9j33-wj62 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-28 00:38 UTCEG score recompute
Related CVEs(same product + same vendor + 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
Same vendor
10 shownredhat:RHSA-2026:72712 · redhat:RHSA-2026:76788
Frequently asked(5)
What is CVE-2026-92942?
When was CVE-2026-92942 made public?
Is CVE-2026-92942 actively exploited?
What is the CVSS score of CVE-2026-92942?
How do I remediate CVE-2026-92942?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-92942
Is Your Infrastructure Affected by CVE-2026-92942?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.