# CVE-2026-110111: Xen Orchestra before 6.9.0 Privilege Escalation via Prototype Pollution in vm.importFromEsxi

> Authenticated users can escalate to global administrator and execute code via prototype pollution in Xen Orchestra's ESXi import methods.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:P/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:** 13 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-9p53-2254-x397, UBUNTU-CVE-2026-110111

## What is CVE-2026-110111?

CVE-2026-110111 is a high-severity vulnerability in vatesfr xen-orchestra, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Xen Orchestra before 6.9.0 contains an improper access control vulnerability that allows any authenticated user to become global administrator by abusing the unprotected vm.importFromEsxi and vm.importMultipleFromEsxi methods. Attackers can point xo-server at a malicious ESXi host serving a crafted .vmx file with __proto__.permission set, polluting Object.prototype so permission-less accounts inherit admin rights and enabling remote code execution.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

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


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

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

## Is CVE-2026-110111 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110111 is a high-severity vulnerability in vatesfr xen-orchestra, published on 13 Oct 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-110111 in the wild and no public exploit code.

Affected product: vatesfr xen-orchestra. 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-110111/ (Markdown: https://insights.sbomify.com/CVE-2026-110111/index.md)
```

## Sources

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

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