CVE-2026-88006: Open WebUI OAuth endpoint skips

Q: Is CVE-2026-88006 actively exploited?

No confirmed active exploitation of CVE-2026-88006 has been reported, but organizations should still patch proactively.

Q: How to fix CVE-2026-88006?

Upgrade to Open WebUI 0.11.1 or later immediately, where the OAuth token exchange endpoint now runs the same role-management checks as the standard login callback. Until patched, audit all OAuth-provisioned accounts and cross-check their current provider-side role/group membership against their in-app Open WebUI role — flag any privileged account whose provider access was recently reduced. Review access and admin-action logs for accounts with elevated Open WebUI roles that no longer match their identity provider's group assignments. Consider temporarily disabling the token exchange flow or restricting it via reverse-proxy rules if immediate patching isn't feasible, and rotate any credentials/API keys accessible to admin-level accounts once the audit is complete.

Q: What systems are affected by CVE-2026-88006?

This vulnerability affects the following AI/ML architecture patterns: model serving, agent frameworks.

Q: What is the CVSS score for CVE-2026-88006?

CVE-2026-88006 has a CVSS v3.1 base score of 6.5 (MEDIUM). The EPSS exploitation probability is 0.22%.

CISO Take

Open WebUI's OAuth token exchange endpoint issues a valid session using the provider's access token without running the same role-management logic that the normal OAuth login callback enforces, so a user whose provider roles should trigger a login refusal or a role demotion can instead retain their prior elevated access simply by hitting this alternate endpoint. With 3 downstream dependents on this package and 168 other CVEs already logged against open-webui, this is a low-friction authorization bypass in a widely self-hosted AI platform, though the impact is capped at retaining an existing session role rather than granting new privileges, and there's no CISA KEV listing, no EPSS score, and no public exploit or Nuclei template tracked yet. CVSS 6.5 (network, no auth, no user interaction) reflects a confidentiality/integrity hit with no availability impact. Patch to Open WebUI 0.11.1 or later, then audit OAuth-linked accounts for anyone whose provider role changed recently but who retained elevated access in Open WebUI, and review session/audit logs around the token exchange endpoint for anomalous role-persistence patterns.

Sources: NVD GitHub Advisory ATLAS

What is the risk?

Medium severity (CVSS 6.5) authorization flaw. Exploitability is straightforward for any authenticated OAuth user (no special tooling or AI/ML expertise required), but exploitation only benefits users who are already provisioned via OAuth and whose provider-side role was demoted or revoked — it does not grant access to arbitrary outsiders. No KEV listing, no EPSS data, and no public exploit code reduce near-term mass-exploitation risk, but the low complexity and lack of required user interaction mean a malicious or disgruntled insider with declining provider permissions can trivially retain stale privileged access.

How does the attack unfold?

Initial Access

Attacker authenticates via an OAuth provider account that previously had elevated Open WebUI access.

AML.T0012

Privilege Retention

Provider-side role demotion or refusal occurs, but the user routes through the OAuth token exchange endpoint instead of the standard login callback.

AML.T0012

Exploitation

The token exchange endpoint issues a session without re-running role management, so the stale elevated role is honored.

Impact

Attacker retains unauthorized elevated access to Open WebUI admin functions, configurations, or other users' data despite provider-side revocation.

Initial Access

Attacker authenticates via an OAuth provider account that previously had elevated Open WebUI access.

AML.T0012

Privilege Retention

Provider-side role demotion or refusal occurs, but the user routes through the OAuth token exchange endpoint instead of the standard login callback.

AML.T0012

Exploitation

The token exchange endpoint issues a session without re-running role management, so the stale elevated role is honored.

Impact

Attacker retains unauthorized elevated access to Open WebUI admin functions, configurations, or other users' data despite provider-side revocation.

What systems are affected?

Package	Ecosystem	Vulnerable Range	Patched
Open WebUI	pip	>= 0.8.0, < 0.11.1	`0.11.1`
151.8K 3 dependents Pushed 7d ago 83% patched ~5d to patch Full package profile →

Do you use Open WebUI? You're affected.

How severe is it?

CVSS 3.1

6.5 / 10

EPSS

0.2%

chance of exploitation in 30 days

Higher than 12% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

No known exploitation

Sophistication

Trivial

What is the attack surface?

AV Network

AC Low

PR None

UI None

S Unchanged

C Low

I Low

A None

What should I do?

1 step

Upgrade to Open WebUI 0.11.1 or later immediately, where the OAuth token exchange endpoint now runs the same role-management checks as the standard login callback. Until patched, audit all OAuth-provisioned accounts and cross-check their current provider-side role/group membership against their in-app Open WebUI role — flag any privileged account whose provider access was recently reduced. Review access and admin-action logs for accounts with elevated Open WebUI roles that no longer match their identity provider's group assignments. Consider temporarily disabling the token exchange flow or restricting it via reverse-proxy rules if immediate patching isn't feasible, and rotate any credentials/API keys accessible to admin-level accounts once the audit is complete.

What does CISA's SSVC say?

Decision Track

Exploitation none

Automatable Yes

Technical Impact partial

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Auth Bypass Framework AML.T0012 - Valid Accounts

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001

A.8 - Resource and access management for AI systems

NIST AI RMF

GOVERN 1.5 - Ongoing monitoring and periodic review of risk management processes, including for access control effectiveness

Frequently Asked Questions

What is CVE-2026-88006?

Open WebUI's OAuth token exchange endpoint issues a valid session using the provider's access token without running the same role-management logic that the normal OAuth login callback enforces, so a user whose provider roles should trigger a login refusal or a role demotion can instead retain their prior elevated access simply by hitting this alternate endpoint. With 3 downstream dependents on this package and 168 other CVEs already logged against open-webui, this is a low-friction authorization bypass in a widely self-hosted AI platform, though the impact is capped at retaining an existing session role rather than granting new privileges, and there's no CISA KEV listing, no EPSS score, and no public exploit or Nuclei template tracked yet. CVSS 6.5 (network, no auth, no user interaction) reflects a confidentiality/integrity hit with no availability impact. Patch to Open WebUI 0.11.1 or later, then audit OAuth-linked accounts for anyone whose provider role changed recently but who retained elevated access in Open WebUI, and review session/audit logs around the token exchange endpoint for anomalous role-persistence patterns.

Is CVE-2026-88006 actively exploited?

No confirmed active exploitation of CVE-2026-88006 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-88006?

Upgrade to Open WebUI 0.11.1 or later immediately, where the OAuth token exchange endpoint now runs the same role-management checks as the standard login callback. Until patched, audit all OAuth-provisioned accounts and cross-check their current provider-side role/group membership against their in-app Open WebUI role — flag any privileged account whose provider access was recently reduced. Review access and admin-action logs for accounts with elevated Open WebUI roles that no longer match their identity provider's group assignments. Consider temporarily disabling the token exchange flow or restricting it via reverse-proxy rules if immediate patching isn't feasible, and rotate any credentials/API keys accessible to admin-level accounts once the audit is complete.

What systems are affected by CVE-2026-88006?

This vulnerability affects the following AI/ML architecture patterns: model serving, agent frameworks.

What is the CVSS score for CVE-2026-88006?

CVE-2026-88006 has a CVSS v3.1 base score of 6.5 (MEDIUM). The EPSS exploitation probability is 0.22%.

What is the AI security impact?

Affected AI Architectures

model servingagent frameworks

MITRE ATLAS Techniques

AML.T0012 Valid Accounts

Compliance Controls Affected

ISO 42001: A.8

NIST AI RMF: GOVERN 1.5

What are the technical details?

Original Advisory

Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.8.0 until 0.11.1, Open WebUI's OAuth token exchange endpoint issues a session for a provider access token without running the OAuth role management that the normal OAuth login callback runs. A user whose provider roles the login callback would refuse, or would demote, could still obtain a working session at their existing role through this endpoint. This issue is fixed in version 0.11.1.

Exploitation Scenario

An employee or contractor loses admin/privileged group membership in the corporate identity provider (e.g., removed from an Okta/Azure AD group tied to Open WebUI admin access) but their existing Open WebUI session or refresh flow routes through the OAuth token exchange endpoint rather than the standard login callback. Because that endpoint skips role re-evaluation, the demoted user continues operating with their old elevated role — accessing admin settings, other users' chat histories, or connected model/API credentials — even though the identity provider has already revoked that trust. No injected prompts, adversarial inputs, or model manipulation are needed; this is a pure identity/session-management gap in the platform wrapping the AI models.

Weaknesses (CWE)

CWE-863 Incorrect Authorization Primary CWE-863 Incorrect Authorization

CWE-863 — Incorrect Authorization: The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

[Architecture and Design] Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
[Architecture and Design] Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].

Source: MITRE CWE corpus.