PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-88006 open-webui CVE debrief

Open WebUI, a self-hosted AI platform, had a vulnerability in its OAuth token exchange endpoint from version 0.8.0 to 0.11.1. This endpoint would issue a session for a provider access token without properly running OAuth role management, unlike the normal OAuth login callback. Consequently, a user whose provider roles the login callback would refuse or demote could still obtain a working session at their existing role through this endpoint. The issue was fixed in version 0.11.1.

Vendor
open-webui
Product
Unknown
CVSS
MEDIUM 6.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-10
Original CVE updated
2026-09-18
Advisory published
2026-09-10
Advisory updated
2026-09-18

Who should care

Defenders managing Open WebUI deployments, especially those using versions between 0.8.0 and 0.11.1, should assess their exposure and consider upgrading to version 0.11.1 or later.

Why it matters

Defenders should care about CVE-2026-88006 because it affects Open WebUI's OAuth role management, potentially allowing users to retain higher privileges than intended. This requires verification of deployment exposure, especially for versions between 0.8.0 and 0.11.1, and consideration of compensating controls.

  • Potential unauthorized privilege retention
  • Need for verification of deployment exposure
  • Possible impact on access control
  • Requires review of OAuth role management configuration

Technical summary

The Open WebUI OAuth token exchange endpoint did not properly enforce OAuth role management from version 0.8.0 to 0.11.1. This allowed users to potentially retain higher privileges than intended. The issue was fixed in version 0.11.1. Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. 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. Defenders managing Open WebUI deployments, especially those using versions between 0.8.0 and 0.11.1, should assess their exposure and consider upgrading to version 0.11.1 or later.

Defensive priority

Defenders should prioritize verifying their Open WebUI deployment's exposure, especially if they are using versions between 0.8.0 and 0.11.1, and assess whether any compensating controls are in place.

Recommended defensive actions

  • Verify Open WebUI deployment version and assess exposure
  • Review OAuth role management configuration
  • Consider upgrading to version 0.11.1 or later
  • Monitor for unusual session activity
  • Track exceptions and retest remediated assets
  • Check relevant monitoring, detection, and logs for exposed assets
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impact, and the fix in version 0.11.1. However, there is limited information on actual exploitation or affected deployments. Open WebUI's OAuth token exchange endpoint did not enforce OAuth role management properly from version 0.8.0 to 0.11.1. This allowed users to potentially retain higher privileges than intended. The issue was fixed in version 0.11.1. Defenders should verify their Open WebUI deployment's exposure, review OAuth role management configuration, and

Sources and references

Verified primary and authoritative sources

  • CVE-2026-88006 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-88006

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-88006 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-88006

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.