CVE-2026-92951

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 week
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.9Exploit: None knownExposed: 0

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

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.

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 computed
Severity99% × 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, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

vm2 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-resolver
github Patch Available🟡 PoC Available

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

Vendor 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.

  1. 2026-09-19 09:48 UTCGHSA enrichment
  2. 2026-09-19 06:03 UTCGHSA enrichment
  3. 2026-09-19 02:19 UTCGHSA enrichment
  4. 2026-09-18 22:35 UTCEG score recompute
  5. 2026-09-18 22:35 UTCGHSA enrichment
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-18 18:51 UTCGHSA enrichment
  8. 2026-09-18 15:06 UTCGHSA enrichment
  9. 2026-09-18 11:23 UTCGHSA enrichment
  10. 2026-09-18 07:39 UTCGHSA enrichment
  11. 2026-09-18 03:55 UTCGHSA enrichment
  12. 2026-09-18 00:11 UTCGHSA enrichment
  13. 2026-09-17 20:27 UTCEG score recompute
  14. 2026-09-17 20:27 UTCGHSA enrichment
  15. 2026-09-17 19:30 UTCEG score recompute
  16. 2026-09-17 19:30 UTCGHSA enrichment
  17. 2026-09-17 18:18 UTCEG score recompute
  18. 2026-09-17 18:18 UTCGHSA enrichment
  19. 2026-09-17 14:22 UTCEG score recompute
  20. 2026-09-17 13:50 UTCEG score recompute
  21. 2026-09-17 13:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92951?
CVE-2026-92951 is a critical vulnerability published on September 17, 2026. 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…
When was CVE-2026-92951 disclosed?
CVE-2026-92951 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-92951 actively exploited?
CVE-2026-92951 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.2% of all scored CVEs.
What is the CVSS score of CVE-2026-92951?
CVE-2026-92951 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-92951?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92951, 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-92951

Explore →

Is Your Infrastructure Affected by CVE-2026-92951?

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