# CVE-2026-84165: Lack of authorisation in OpenNebula by OpenNebula Systems

> Authenticated users can execute commands on other users' virtual machines if qemu-agent is enabled, leading to potential compromise.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-m4j2-w8wf-vp83, UBUNTU-CVE-2026-84165

## What is CVE-2026-84165?

CVE-2026-84165 is a high-severity missing authorization vulnerability in OpenNebula, published on 1 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-84165?


## How do I fix CVE-2026-84165?

No fix has been published for CVE-2026-84165 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-84165 being exploited?

There is no known exploitation of CVE-2026-84165 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84165 and fix it if it is affected.

What it is: CVE-2026-84165 is a high-severity missing authorization vulnerability in OpenNebula, published on 1 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84165 in the wild and no public exploit code.

Affected product: OpenNebula. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84165/ (Markdown: https://insights.sbomify.com/CVE-2026-84165/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84165
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84165
- OSV: https://osv.dev/vulnerability/CVE-2026-84165

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84165/
Summaries are generated and may contain mistakes; the official description above is the record.