CVE-2026-92939

CRITICALPre-NVD 9.99.9—
EchelonGraph scoreHIGH confidence

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

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.9
EG Score
9.9(high)
EG Risk
61(Track*)
EG Risk 61/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 computed
Severity99% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 17, 2026

Advisory Details (2)

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

vm2 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-xffx
generic

vm2 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-setengine

Vendor Advisories for CVE-2026-92939(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 18× in last 7d / 18× 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-09-19 05:49 UTCGHSA enrichment
  2. 2026-09-19 02:03 UTCGHSA enrichment
  3. 2026-09-18 22:18 UTCEG score recompute
  4. 2026-09-18 22:18 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 18:33 UTCGHSA enrichment
  7. 2026-09-18 14:44 UTCGHSA enrichment
  8. 2026-09-18 10:59 UTCGHSA enrichment
  9. 2026-09-18 07:14 UTCGHSA enrichment
  10. 2026-09-18 03:29 UTCGHSA enrichment
  11. 2026-09-17 23:43 UTCGHSA enrichment
  12. 2026-09-17 19:12 UTCEG score recompute
  13. 2026-09-17 19:11 UTCGHSA enrichment
  14. 2026-09-17 15:22 UTCEG score recompute
  15. 2026-09-17 14:34 UTCEG score recompute
  16. 2026-09-17 14:23 UTCEG score recompute
  17. 2026-09-17 13:50 UTCEG score recompute
  18. 2026-09-17 13:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92939?
CVE-2026-92939 is a critical vulnerability published on September 17, 2026. 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…
When was CVE-2026-92939 disclosed?
CVE-2026-92939 was first published in the National Vulnerability Database on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92939 actively exploited?
CVE-2026-92939 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.0% of all scored CVEs.
What is the CVSS score of CVE-2026-92939?
CVE-2026-92939 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-92939?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92939, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-92939?

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

Start Free Scan →Browse All CVEs