# CVE-2026-109572: Open WebUI 0.8.6 before 0.11.4 Privilege Escalation via Terminal Proxy

> Authenticated users can escalate privileges via the terminal proxy to manage other users' terminals and inject environment variables.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/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:** 12 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-865q-vfjv-p93j, GHSA-q46m-r89w-j74p

## What is CVE-2026-109572?

CVE-2026-109572 is a high-severity vulnerability in open-webui, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Open WebUI from 0.8.6 before 0.11.4 contains a privilege escalation vulnerability in the terminal proxy that allows authenticated users to reach the Terminals administrator API with the shared key attached. Attackers can send requests through /api/v1/terminals/{server_id}/{path} to list or stop other users' terminals and modify terminal policies, injecting environment variables into other users' terminals.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-109572 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109572 is a high-severity vulnerability in open-webui, published on 12 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-109572 in the wild and no public exploit code.

Affected product: open-webui. 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-109572/ (Markdown: https://insights.sbomify.com/CVE-2026-109572/index.md)
```

## Sources

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

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