# CVE-2026-109292: Open WebUI 0.6.27 before 0.11.4 Session Token Disclosure via OAuth-Mode Connections

> Attackers controlling OAuth-mode connections can steal user session cookies to hijack accounts, including administrators, in Open WebUI.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-crcq-c44m-c92x, GHSA-gqfh-jxvw-74rp

## What is CVE-2026-109292?

CVE-2026-109292 is a high-severity vulnerability in open-webui, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Open WebUI from 0.6.27 before 0.11.4 contains an information disclosure vulnerability that allows destination servers to obtain user session cookies by receiving the full browser cookie jar on OAuth-mode connections. Operators of OpenAI-compatible connections, OpenAPI tool servers or terminal servers can capture forwarded session cookies from routine requests and replay them to hijack accounts, including administrators.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-109292 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109292 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109292 is a high-severity vulnerability in open-webui, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109292 exists.

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-109292/ (Markdown: https://insights.sbomify.com/CVE-2026-109292/index.md)
```

## Sources

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

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