CVE-2026-84165

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
8.7EG
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.4%CVSS: 8.7Exploit: None knownExposed services: Not assessed

Update to OpenNebula version 7.4 (from the CVE record's solution, Spanish National Cybersecurity Institute, S.A. (INCIBE)) — apply it.

A vulnerability relating to incorrect access control in OpenNebula by OpenNebula Systems, affecting all versions prior to 7.4. This vulnerability could allow an authenticated user with basic permissions to execute commands on virtual machines belonging to other users via the one.vm.exec function, without proper verification of access permissions. To exploit the vulnerability, it is only necessary to know the virtual machine’s identifier and for qemu-agent to be enabled on that machine. Exploitation could allow commands to be executed and compromise the confidentiality, integrity and availability of the affected virtual machines.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
39
EG Risk 39/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)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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: Update to OpenNebula version 7.4 (from the CVE record's solution, Spanish National Cybersecurity Institute, S.A. (INCIBE)). Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
36th
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 (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-18). 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: 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).

Update to OpenNebula version 7.4 (from the CVE record's solution, Spanish National Cybersecurity Institute, S.A. (INCIBE)). 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.

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 1, 2026

Last Modified

September 1, 2026

Advisory Details (1)

Auto-updated Sep 1, 2026
Fix named in the CVE record's solution (Spanish National Cybersecurity Institute, S.A. (INCIBE)).
Web page

Lack of authorisation in OpenNebula by OpenNebula Systems | INCIBE-CERT | INCIBE

https://www.incibe.es/en/incibe-cert/notices/aviso/lack-authorisation-opennebula-opennebula-systems

Vendor Advisories for CVE-2026-84165(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 10× in last 7d / 91× 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 163 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 63 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-84165?
CVE-2026-84165 is a high-severity vulnerability; its CVE record was published on September 1, 2026. A vulnerability relating to incorrect access control in OpenNebula by OpenNebula Systems, affecting all versions prior to 7.4. This vulnerability could allow an authenticated user with basic permissions to execute commands on virtual machines belonging to other users via the one.vm.exec function,…
When was CVE-2026-84165 made public?
CVE-2026-84165 was made public on September 1, 2026: that is the date its CVE record's CNA, Spanish National Cybersecurity Institute, S.A. (INCIBE), gives for when the vulnerability was made public. The CVE record itself was published on September 1, 2026. EchelonGraph's copy of the record carries a last-modified date of September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-84165 actively exploited?
CVE-2026-84165 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84165?
CVE-2026-84165 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-84165?
The CVE record's solution for CVE-2026-84165, written by its CNA Spanish National Cybersecurity Institute, S.A. (INCIBE), names the fix: "Update to OpenNebula version 7.4." The vendor advisories EchelonGraph has for CVE-2026-84165 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-84165?

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