Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-87016 – Authentication Bypass / Account Takeover – Open WebUI 0.6.41–0.11.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-87016 is a high-severity authentication bypass in Open WebUI affecting deployments that use a SQLite database. The flaw allows an attacker who controls or supplies an OAuth/OIDC or SCIM subject identifier to sign in as an arbitrary existing user, including administrators, without knowing that user’s credentials. It carries a CVSS v3.1 base score of 8.1 (High).

Technical details

  • Root cause: the identity-lookup functions get_user_by_oauth_sub and get_user_by_scim_external_id perform user resolution using a SQL LIKE comparison against serialized JSON on SQLite, rather than an exact-match comparison.
  • Trigger condition: a subject value containing SQL wildcard characters (% or _) causes the LIKE query to match accounts the value was never issued for; the login then binds to whichever matching account the database returns first.
  • Attack vector: network — requires OAuth/OIDC sign-in or SCIM provisioning to be enabled on a SQLite-backed Open WebUI instance, and the attacker to control or influence the subject claim value used during sign-in.
  • Impact: unauthorized sign-in as another user, up to and including an administrator account, resulting in full compromise of confidentiality, integrity, and availability of the affected instance.
  • PostgreSQL-backed deployments are not vulnerable, as they use a separate, exact-match code path.

Affected software

  • Open WebUI versions 0.6.41 through 0.11.0 (inclusive), when configured with a SQLite database.
  • Fixed in version 0.11.1.

Severity

  • CVSS v3.1 Base Score: 8.1 (High)
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Open WebUI to version 0.11.1 or later. No configuration changes are required after upgrading; existing stored identities are unaffected.
  • If immediate patching is not possible: consider disabling OAuth/OIDC sign-in and SCIM provisioning, or migrate the deployment’s database backend from SQLite to PostgreSQL, which is not affected by this issue.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Open WebUI
  • Raw response body: Search Open WebUI, <ShortName>Open WebUI</ShortName>

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge