vm2 before 3.11.7 contains an incorrect authorization vulnerability in the external package allowlist check that uses non-exact substring matching instead of full package-name boundary validation. Attackers can bypass the allowlist by requiring a colliding package name that contains an allowlisted package substring, causing vm2 to load and execute unauthorized host packages in the host context.
CVE-2026-92951
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.
- 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
- 9.9
- EG Score
- 9.9(high)
- EG Risk
- 45(Track)EG Risk 45/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 computedSeverity99% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
September 17, 2026
Last Modified
September 17, 2026
Advisory Details (2)
Auto-updated Sep 17, 2026vm2 before 3.11.7 Module Allowlist Bypass via Custom Resolver | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vm2-before-3.11.7-module-allowlist-bypass-via-custom-resolvervm2 Custom Module Resolver Can Bypass the External Package Allowlist by Loading a Colliding Host Package · Advisory · patriksimek/vm2 · GitHub
https://github.com/patriksimek/vm2/security/advisories/GHSA-c48m-32m9-vx93Vendor Advisories for CVE-2026-92951(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 21× in last 7d / 21× 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 09:48 UTCGHSA enrichment
- 2026-09-19 06:03 UTCGHSA enrichment
- 2026-09-19 02:19 UTCGHSA enrichment
- 2026-09-18 22:35 UTCEG score recompute
- 2026-09-18 22:35 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:51 UTCGHSA enrichment
- 2026-09-18 15:06 UTCGHSA enrichment
- 2026-09-18 11:23 UTCGHSA enrichment
- 2026-09-18 07:39 UTCGHSA enrichment
- 2026-09-18 03:55 UTCGHSA enrichment
- 2026-09-18 00:11 UTCGHSA enrichment
- 2026-09-17 20:27 UTCEG score recompute
- 2026-09-17 20:27 UTCGHSA enrichment
- 2026-09-17 19:30 UTCEG score recompute
- 2026-09-17 19:30 UTCGHSA enrichment
- 2026-09-17 18:18 UTCEG score recompute
- 2026-09-17 18:18 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-92951?
When was CVE-2026-92951 disclosed?
Is CVE-2026-92951 actively exploited?
What is the CVSS score of CVE-2026-92951?
How do I remediate CVE-2026-92951?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-92951
Is Your Infrastructure Affected by CVE-2026-92951?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.