Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-wpmr-8h3q-fwj7

Open WebUI: Sign-in as another user via wildcard characters in the OAuth subject claim on SQLite

CVSS 8.1 HighEPSS 0.0060 · 48th percentile

Published by the GitHub Advisory Database at 10 Sept 2026, 21:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
open-webuiPyPI>=0.6.41, <0.11.10.11.1
Identifiers
GHSA-wpmr-8h3q-fwj7 · CVE-2026-87016 · PYSEC-2026-4128
Weakness (CWE)
CWE-155 · CWE-287
Tags
Published
10 Sept 2026
Updated
1 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Open WebUI versions 0.6.41 up to but not including 0.11.1 are vulnerable on SQLite deployments, where OAuth/OIDC external identity lookup and SCIM external-ID resolution use substring matching instead of exact matching. An attacker who can set the subject claim at the identity provider (only when the operator has configured a user-settable claim) can sign in as another account, including an administrator; otherwise, subject values containing underscores can resolve to the wrong account. Upgrade to Open WebUI 0.11.1, which fixes the issue with no configuration change required.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.1 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0060, the 48th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:09 UTC First seen by agentprime
  2. 31 Oct 2026, 14:09 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.