CVE-2026-92951

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

“—” 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.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week

Also known asEUVD-2026-81600 (ENISA EUVD) · GHSA-6fvh-fgmg-3x7v (GitHub Security Advisories) · GHSA-c48m-32m9-vx93 (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/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.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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.
EPSS PROB
0.5%
EPSS %ILE
40th
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.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; Track* at high (mission-essential systems).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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (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, 2026
🔬 Proof of concept available. Patch available. Sources: github.
Web page

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 advisoryMentions a patch (unverified)🟡 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(7)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:17931178132026-10-28redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17918656602026-10-13redhat
redhatansible-automation-platform/automation-portal:17912953792026-10-12redhat
redhatansible-automation-platform/automation-portal:17912937802026-10-12redhat
redhatrhdh/rhdh-hub-rhel9:17913114952026-10-08redhat
redhatrhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:17912512822026-10-06redhat
npmvm2 @ 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)
PackageVulnerable rangeFix by version rangeDependents
vm2—
  • every version up to 3.11.7: fixed in 3.11.7
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 23× in last 7d / 118× 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 242 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 142 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-11-01 08:41 UTCVendor advisory
  3. 2026-11-01 08:41 UTCGHSA enrichmentGHSA-c48m-32m9-vx93 · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-c48m-32m9-vx93 · GitHub severity CRITICAL · GitHub CVSS 9.9
  5. 2026-11-01 07:37 UTCEG score recompute
  6. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-10-31 09:20 UTCEG score recompute
  8. 2026-10-31 09:20 UTCVendor advisory
  9. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-30 09:59 UTCEG score recompute
  11. 2026-10-30 09:59 UTCVendor advisory
  12. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  13. 2026-10-29 10:39 UTCEG score recompute
  14. 2026-10-29 10:39 UTCVendor advisory
  15. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  16. 2026-10-28 11:14 UTCEG score recompute
  17. 2026-10-28 11:14 UTCVendor advisory
  18. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  19. 2026-10-27 11:14 UTCEG score recompute
  20. 2026-10-27 11:14 UTCVendor advisory
  21. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  22. 2026-10-26 11:54 UTCEG score recompute
  23. 2026-10-26 11:54 UTCVendor advisory
  24. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  25. 2026-10-25 13:50 UTCEG score recompute
Show 75 more
  1. 2026-10-25 12:18 UTCEG score recompute
  2. 2026-10-25 12:18 UTCVendor advisory
  3. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-10-24 12:52 UTCEG score recompute
  5. 2026-10-24 12:52 UTCVendor advisory
  6. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-10-23 13:26 UTCEG score recompute
  8. 2026-10-23 13:26 UTCVendor advisory
  9. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  10. 2026-10-22 14:02 UTCEG score recompute
  11. 2026-10-22 14:02 UTCVendor advisory
  12. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  13. 2026-10-21 14:38 UTCEG score recompute
  14. 2026-10-21 14:38 UTCVendor advisory
  15. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-10-20 14:50 UTCEG score recompute
  17. 2026-10-20 14:50 UTCVendor advisory
  18. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  19. 2026-10-19 14:18 UTCEG score recompute
  20. 2026-10-19 14:18 UTCVendor advisory
  21. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  22. 2026-10-18 14:56 UTCVendor advisory
  23. 2026-10-18 02:59 UTCEG score recompute
  24. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  25. 2026-10-17 15:34 UTCEG score recompute
  26. 2026-10-17 15:34 UTCVendor advisory
  27. 2026-10-17 06:22 UTCEG score recompute
  28. 2026-10-17 06:22 UTCVendor advisory
  29. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  30. 2026-10-16 06:59 UTCEG score recompute
  31. 2026-10-16 06:59 UTCVendor advisory
  32. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  33. 2026-10-15 05:42 UTCEG score recompute
  34. 2026-10-15 05:42 UTCVendor advisory
  35. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  36. 2026-10-14 01:20 UTCEG score recompute
  37. 2026-10-14 01:20 UTCVendor advisory
  38. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  39. 2026-10-12 21:33 UTCEG score recompute
  40. 2026-10-12 21:33 UTCVendor advisory
  41. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  42. 2026-10-12 14:44 UTCEG score recompute
  43. 2026-10-12 02:26 UTCVendor advisory
  44. 2026-10-11 22:42 UTCVendor advisory
  45. 2026-10-11 19:12 UTCEG score recompute
  46. 2026-10-11 18:57 UTCVendor advisory
  47. 2026-10-11 16:29 UTCEG score recompute
  48. 2026-10-11 15:11 UTCEG score recompute
  49. 2026-10-11 15:11 UTCVendor advisory
  50. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  51. 2026-10-11 13:43 UTCEG score recompute
  52. 2026-10-11 11:24 UTCEG score recompute
  53. 2026-10-11 11:24 UTCVendor advisory
  54. 2026-10-11 07:36 UTCVendor advisory
  55. 2026-10-11 03:43 UTCVendor advisory
  56. 2026-10-10 20:27 UTCEG score recompute
  57. 2026-10-10 20:27 UTCVendor advisory
  58. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  59. 2026-10-10 16:36 UTCVendor advisory
  60. 2026-10-10 12:52 UTCVendor advisory
  61. 2026-10-10 09:02 UTCVendor advisory
  62. 2026-10-10 05:18 UTCVendor advisory
  63. 2026-10-10 01:33 UTCVendor advisory
  64. 2026-10-09 21:46 UTCEG score recompute
  65. 2026-10-09 21:46 UTCVendor advisory
  66. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  67. 2026-10-09 18:01 UTCVendor advisory
  68. 2026-10-09 13:30 UTCVendor advisory
  69. 2026-10-09 09:02 UTCVendor advisory
  70. 2026-10-09 05:17 UTCVendor advisory
  71. 2026-10-09 01:33 UTCVendor advisory
  72. 2026-10-08 21:49 UTCVendor advisory
  73. 2026-10-08 18:03 UTCEG score recompute
  74. 2026-10-08 18:03 UTCVendor advisory
  75. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.5% · 43rd percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-92951?
CVE-2026-92951 is a critical-severity vulnerability; its CVE record was 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 made public?
CVE-2026-92951 was made public on August 24, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 17, 2026. EchelonGraph's copy of the record carries a last-modified date of September 17, 2026; the record at its source may have been updated since.
Is CVE-2026-92951 actively exploited?
CVE-2026-92951 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92951?
CVE-2026-92951 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92951?
A fix for CVE-2026-92951 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-92951 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs