# CVE-2026-70482: Open WebUI: Account takeover via OAuth token exchange accepting tokens issued to any client

> Attackers can hijack user accounts by exchanging OAuth tokens issued to any client when token exchange is enabled.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A: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:** Yes
- **Published:** 4 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-rq84-p6rr-vf89, PYSEC-2026-3652

## What is CVE-2026-70482?

CVE-2026-70482 is a high-severity authentication bypass vulnerability in Openwebui Open Webui, published on 4 Aug 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 is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.8.0 until 0.11.0, when ENABLE_OAUTH_TOKEN_EXCHANGE=True, /oauth/{provider}/token/exchange accepts a raw provider access token and validates it by calling the provider userinfo endpoint without confirming which OAuth client the token was issued to. Anyone holding an access token minted for any client registered with the same provider could exchange it for an Open WebUI session as that token user, including applications the operator does not control and has never authorized. This issue is fixed in 0.11.0.

Weakness: CWE-287 (Improper Authentication)

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

3 open source packages ship an affected version, including open-webui. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `open-webui` | PyPI | From 0.8.0 | 0.11.0 |
| `open-webui` | PyPI | From 0.8.0 | 0.11.0 |
| `open-webui` | PyPI | From 0.8.0 | 0.11.0 |

Products: Openwebui Open Webui.

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

Upgrade open-webui to 0.11.0 or later.

## Is CVE-2026-70482 being exploited?

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

## Other vulnerabilities in Openwebui Open Webui

- [CVE-2026-44551](https://insights.sbomify.com/CVE-2026-44551/): Open WebUI: LDAP Empty Password Authentication Bypass (critical 9.1)
- [CVE-2026-56400](https://insights.sbomify.com/CVE-2026-56400/): open-webui - Remote Code Execution via CORS Misconfiguration and Session Validation (critical 9.0)
- [CVE-2024-8017](https://insights.sbomify.com/CVE-2024-8017/): Cross-site Scripting (XSS) in open-webui/open-webui (critical 9.0)
- [CVE-2026-45672](https://insights.sbomify.com/CVE-2026-45672/): Open WebUI: Jupyter code execution works despite `ENABLE_CODE_EXECUTION=false` — feature gate bypassed (high 8.8)
- [CVE-2026-87995](https://insights.sbomify.com/CVE-2026-87995/): Open WebUI: Same-origin XSS to account takeover via terminal port-preview iframe hardcoding allow-same-origin (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70482 is a high-severity authentication bypass vulnerability in Openwebui Open Webui, published on 4 Aug 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: There is no known exploitation of CVE-2026-70482 in the wild and no public exploit code.

Affected packages and fixed versions:
- open-webui (PyPI): affected from 0.8.0; fixed in 0.11.0
- open-webui (PyPI): affected from 0.8.0; fixed in 0.11.0
- open-webui (PyPI): affected from 0.8.0; fixed in 0.11.0

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

## Sources

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

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