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.
Affected products
openwebui: open webui
References5
- github.com/open-webui/open-webui/security/advisories/GHSA-rq84-… ExploitMitigationVendor Advisory
- github.com/open-webui/open-webui/security/advisories/GHSA-rq84-… ExploitMitigationVendor Advisory
- github.com/open-webui/open-webui/commit/b190dcf3caa00dc8b7b9c73… Patch
- github.com/open-webui/open-webui/commit/c4332be71e6e9c314e8a13b… Patch
- github.com/open-webui/open-webui/releases/tag/v0.11.0 Release Notes
Metrics
- CVSS 3.1
-
8.8
HIGH
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 1% percentile: 48 · as of 13 November 2026
- CWE
- CWE-287
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.