Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid provider access token for linked account
-
DeliverySend token to OAuth token-exchange endpoint
-
ExploitServer reads roles from userinfo only, finds none
-
ExecutionPrevious elevated role retained in new session
-
ImpactAuthenticated access with stale privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an existing user account in Open WebUI that is linked to an external OAuth identity provider, plus a currently valid provider access token for that account. The flaw triggers specifically when the identity provider conveys role/authorization claims only in the ID token while omitting them from the userinfo response, and when an OAuth role policy is configured such that the user's current IdP role no longer qualifies for their prior Open WebUI role. The practical attacker is a user whose IdP role was downgraded or revoked but whose Open WebUI session role is not correspondingly demoted. Limiting factors: it does not work against unauthenticated attackers (a valid linked account and token are required), it has no effect if the IdP includes roles in the userinfo response, and it is confined to versions 0.11.1 through 0.11.3; impact is limited to retaining an already-held role, not arbitrary escalation. |
| Impact | This is a genuine but moderate-severity issue, not a top-priority emergency. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) and the 5.3 Medium score are internally consistent with the description: exploitation is network-reachable and low-complexity, but requires PR:L - the attacker must already possess a valid, linked account and a working provider access token, so this is an authenticated privilege-retention flaw rather than an unauthenticated takeover. Impact is correctly scoped as VC:L/VI:L/VA:N with no scope change, reflecting that the attacker merely retains a previously-held role rather than escalating to arbitrary privileges. No EPSS score, KEV listing, or POC was provided in the input, so there is no signal of active exploitation or published exploit code; the absence of these signals is consistent with a narrow, condition-dependent bug. The practical risk is limited to environments where an identity provider delivers role claims only in the ID token and where a user's role has actually been downgraded or revoked at the IdP - a specific operational scenario. Overall: a legitimate authorization-logic defect worth patching, but lower real-world urgency than the network attack vector alone might suggest. |
| Exploit ScenarioDerived | A former administrator (or other privileged user) whose role was downgraded or revoked at the identity provider still holds a linked Open WebUI account and a valid provider access token. They POST that token to /api/v1/auths/oauth/{provider}/token/exchange; because the server reads roles only from the userinfo response and keeps the existing role when no roles claim is present (ignoring the ID token), the returned session retains their old, higher privilege. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Authorization bypass in Open WebUI 0.11.1 through 0.11.3 allows an authenticated user with a linked OAuth account to retain their previous role after their identity provider role is downgraded or revoked, provided the provider sends role claims only in the ID token and not in the userinfo response. The vulnerability resides in the OAuth token exchange endpoint, which does not demote the user's existing role when no roles claim is found in userinfo. No public exploit has been identified, and impact is limited to retaining an already-held role rather than gaining new privileges.
RemediationAI
Upgrade to Open WebUI 0.11.4 or later, which corrects the OAuth token exchange endpoint to properly read role claims from the ID token when the userinfo response lacks them. If immediate patching is not possible, configure the identity provider to include role claims in the userinfo response, as the vulnerability only triggers when roles are absent there; this requires IdP-side changes and may have broader effects on other applications. Alternatively, manually review and demote any users whose IdP roles have been downgraded but whose Open WebUI roles remain elevated, though this is a temporary measure. Disabling OAuth role synchronization entirely would prevent the bypass but removes legitimate role management. Vendor advisory: https://github.com/open-webui/open-webui/security/advisories/GHSA-2rr4-q6pg-m5g3.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is an incorrect authorization (CWE-863) in Open WebUI's OAuth token exchange endpoint (POST /api/v1/auths/oauth/{provider}/token/exchange). When an existing user with a linked account submits a valid provider access token, the endpoint reads role claims exclusively from the provider's userinfo response. If the identity provider conveys roles only in the ID token, the userinfo response lacks a roles claim, causing Open WebUI to preserve the user's existing role instead of applying the configured OAuth role policy. This occurs when the user's current IdP role no longer satisfies the policy, allowing them to keep a higher role they should have lost. The vulnerability affects Open WebUI versions 0.11.1 up to (but not including) 0.11.4, as identified by CPE cpe:2.3:a:open-webui:open-webui:*:*:*:*:*:*:*:* and reported by VulnCheck.
Know when Open Webui gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Requires a valid linked account and provider token so PR:L; network-reachable and low-complexity; impact limited to retaining an existing role, giving C:L/I:L and A:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
Open WebUI from 0.11.1 before 0.11.4 contains an authorization bypass in the OAuth token exchange endpoint, which reads role claims only from the provider's userinfo response and keeps the user's existing role when no roles claim is found, ignoring roles sent only in the ID token. Users with a linked account whose identity provider role no longer satisfies the OAuth role policy can send a valid provider access token to POST /api/v1/auths/oauth/{provider}/token/exchange to obtain a session retaining their previous role.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Open Webui
View allAn XSS vulnerability exists in open-webui/open-webui versions <= 0.3.8, specifically in the function that constructs the
A Stored Cross-Site Scripting (XSS) vulnerability exists in the chat file upload functionality of open-webui/open-webui
Attacker controlled files can be uploaded to arbitrary locations on the web server's filesystem by abusing a path traver
Stored cross-site scripting in Open WebUI's terminal port preview feature allows an authenticated attacker sharing a ter
Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.6.37, a St
Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.6.37, a Se
In version v0.3.10 of open-webui/open-webui, the `api/v1/utils/pdf` endpoint lacks authentication mechanisms, allowing u
OAuth and SCIM identity confusion in Open WebUI 0.6.41-0.10.x (SQLite-backed deployments only) allows unauthenticated re
DNS rebinding SSRF in Open WebUI versions 0.9.6 through 0.11.0 allows authenticated users who control authoritative DNS
Denial of service in Open WebUI versions 0.9.0-0.11.0 allows unauthenticated remote attackers to stall the application s
In version 0.3.8 of open-webui, an endpoint for converting markdown to HTML is exposed without authentication. Rated hig
Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. [CVSS 7.3 HIGH]
EUVD-2026-97585
GHSA-wr8j-3xx4-g2v5
NVD
CVE.org
EPSS
Exploit-DB