vm2 3.11.3 through 3.11.6 exposes the host Node.js crypto module to a NodeVM sandbox when the crypto builtin is allowed. The module is presented via a recursive read-only proxy, but its callable exports still execute with host-process authority. Sandboxed JavaScript can therefore call crypto.setEngine() with a filesystem path to an attacker-supplied native library (for example, one bundled in an untrusted plugin package already written to disk); OpenSSL asks the operating-system dynamic loader to load the file, and the library's constructor executes native code in the host process before engine-symbol validation rejects it. Exploitation requires only the crypto builtin and does not require fs, process, module, child_process, worker_threads, vm, or inspector access, resulting in a sandbox escape and arbitrary native code execution. Fixed in 3.11.7.
CVE-2026-92939
“—” beside the score: it is equal to the CVSS score beside it.
Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-01. A secondary CVSS source baseline 9.9; sources differ by 0.0.
Also known asEUVD-2026-81589 (ENISA EUVD) · GHSA-46pr-c5wc-xffx (GitHub Security Advisories) · GHSA-6jgm-4w45-vh8j (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
- 9.9
- EG Score
- 9.9CRITICALmedium confidence
- EG Risk
- 61EG Risk 61/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)Severity99% × 45%Impact severity (EG Severity): CVSS 9.9 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.Automatability0% × 15%CISA's SSVC Automatable value: no (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 no (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.6%
- EPSS %ILE
- 49th
- 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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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: 14 days if the affected system is publicly exposed; Fix on system upgrade 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 no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 17, 2026
Last Modified
September 17, 2026
Advisory Details (2)
Auto-updated Oct 30, 2026vm2 3.11.6 crypto builtin loads attacker native code through setEngine · Advisory · patriksimek/vm2 · GitHub
https://github.com/patriksimek/vm2/security/advisories/GHSA-46pr-c5wc-xffxvm2 3.11.3 through 3.11.6 Native Code Execution via crypto.setEngine | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vm2-3.11.3-through-3.11.6-native-code-execution-via-crypto-setengineVendor Advisories for CVE-2026-92939(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:80644Red Hat Product SecurityCritical
Red Hat Security Advisory: Ansible plug-ins for Red Hat Developer Hub Product Release Update
- RHSA-2026:80603Red Hat Product SecurityCritical
Red Hat Security Advisory: Ansible plug-ins for Red Hat Developer Hub Product Release Update
- 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-46pr-c5wc-xffxGitHub Security AdvisoriesCritical
vm2 crypto builtin loads attacker native code through setEngine
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 | ansible-automation-platform/automation-portal:1791295379 | 2026-10-12 | redhat |
| redhat | ansible-automation-platform/automation-portal:1791293780 | 2026-10-12 | 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 |
| npm | vm2 @ 3.11.7 (fixes >= 3.11.3, <= 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(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 22× in last 7d / 117× 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 100 of 238 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. None are among the latest 100 rows. The 138 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 02:07 UTCEG score recompute
- 2026-11-02 02:07 UTCVendor advisory
- 2026-11-02 02:07 UTCGHSA enrichmentGHSA-46pr-c5wc-xffx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-11-01 07:37 UTCGHSA enrichmentGHSA-46pr-c5wc-xffx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-11-01 07:37 UTCEG score recompute
- 2026-10-31 23:42 UTCEG score recompute
- 2026-10-31 23:42 UTCVendor advisory
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-30 21:19 UTCEG score recompute
- 2026-10-30 21:19 UTCVendor advisory
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-29 18:56 UTCEG score recompute
- 2026-10-29 18:56 UTCVendor advisory
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-28 16:33 UTCEG score recompute
- 2026-10-28 16:33 UTCVendor advisory
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-27 14:07 UTCEG score recompute
- 2026-10-27 14:07 UTCVendor advisory
- 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-26 11:08 UTCEG score recompute
- 2026-10-26 11:08 UTCVendor advisory
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
Show 75 moreShow fewer
- 2026-10-25 13:50 UTCEG score recompute
- 2026-10-25 08:46 UTCEG score recompute
- 2026-10-25 08:46 UTCVendor advisory
- 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-24 06:23 UTCEG score recompute
- 2026-10-24 06:23 UTCVendor advisory
- 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-23 04:00 UTCEG score recompute
- 2026-10-23 04:00 UTCVendor advisory
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-22 01:37 UTCEG score recompute
- 2026-10-22 01:37 UTCVendor advisory
- 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-20 23:13 UTCEG score recompute
- 2026-10-20 23:13 UTCVendor advisory
- 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-19 20:50 UTCEG score recompute
- 2026-10-19 20:50 UTCVendor advisory
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-18 17:57 UTCEG score recompute
- 2026-10-18 17:57 UTCVendor advisory
- 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-18 02:59 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-17 15:34 UTCEG score recompute
- 2026-10-17 15:34 UTCVendor advisory
- 2026-10-17 10:32 UTCEG score recompute
- 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-16 08:07 UTCEG score recompute
- 2026-10-16 08:07 UTCVendor advisory
- 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-15 05:42 UTCEG score recompute
- 2026-10-15 05:42 UTCVendor advisory
- 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-14 01:20 UTCEG score recompute
- 2026-10-14 01:20 UTCVendor advisory
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-12 21:33 UTCEG score recompute
- 2026-10-12 21:33 UTCVendor advisory
- 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-12 14:44 UTCEG score recompute
- 2026-10-12 02:30 UTCVendor advisory
- 2026-10-11 22:43 UTCVendor advisory
- 2026-10-11 19:13 UTCEG score recompute
- 2026-10-11 18:57 UTCVendor advisory
- 2026-10-11 16:29 UTCEG score recompute
- 2026-10-11 15:11 UTCEG score recompute
- 2026-10-11 15:11 UTCVendor advisory
- 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-11 13:43 UTCEG score recompute
- 2026-10-11 11:24 UTCEG score recompute
- 2026-10-11 11:24 UTCVendor advisory
- 2026-10-11 07:36 UTCVendor advisory
- 2026-10-11 03:43 UTCVendor advisory
- 2026-10-10 20:27 UTCEG score recompute
- 2026-10-10 20:27 UTCVendor advisory
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-10 16:39 UTCVendor advisory
- 2026-10-10 12:52 UTCVendor advisory
- 2026-10-10 09:04 UTCVendor advisory
- 2026-10-10 05:19 UTCVendor advisory
- 2026-10-10 01:33 UTCVendor advisory
- 2026-10-09 21:49 UTCEG score recompute
- 2026-10-09 21:49 UTCVendor advisory
- 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-09 18:03 UTCVendor advisory
- 2026-10-09 13:35 UTCVendor advisory
- 2026-10-09 09:04 UTCVendor advisory
- 2026-10-09 05:19 UTCVendor advisory
- 2026-10-09 01:34 UTCVendor advisory
- 2026-10-08 21:49 UTCVendor advisory
- 2026-10-08 18:03 UTCEG score recompute
- 2026-10-08 18:03 UTCVendor advisory
- 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-08 09:16 UTCVendor advisory
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:76788
Frequently asked(5)
What is CVE-2026-92939?
When was CVE-2026-92939 made public?
Is CVE-2026-92939 actively exploited?
What is the CVSS score of CVE-2026-92939?
How do I remediate CVE-2026-92939?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-92939
Is Your Infrastructure Affected by CVE-2026-92939?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.