Open WebUI has Improper Authorization Control
CVE-2026-44567GHSA-4vg5-rp28-gvjf
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (open-webui 0.1.124), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI open-webui
- Affected
- <= 0.1.123
- Fixed in
- 0.1.124
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-4vg5-rp28-gvjf lists affected ranges: PyPI open-webui >=0 <0.1.124 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-4vg5-rp28-gvjf lists affected ranges: PyPI open-webui >=0 <=0.1.123
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
- EPSS
- CVE-2026-44567: 0.23% estimated exploitation activity in the next 30 days; percentile 13.94 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
CONFIDENTIAL Vulnerability Disclosure Analysis Documentation --- Vulnerability Details |
| Field | Value | |---|-------|-------| | 1 | Discoverer | Taylor Pennington of KoreLogic, Inc. | | 2 | Date Submitted | June 11, 2024 | | 3 | Title | Open WebUI Improper Authorization Control | | 5 | Affected Vendor | Open WebUI | | 6 | Affected Product(s) | Open WebUI (Formerly Ollama WebUI) | | 7 | Affected Version(s) | 0.1.105 | | 8 | Platform/OS | Debian GNU/Linux 12 (bookworm) | | 9 | Vector | HTTP web interface | | 10 | CWE | 285 Improper Authorization | --- 4. High-level Summary There is a missing authorization check affecting user accounts with a pending status allowing the user to make authenticated API calls as a user context. --- 11. Technical Analysis The Open WebUI web application has three user role classifications: user, admin, and pending. By default, when Open WebUI is configured with new sign-ups enabled, the default user role is set to pending. In this configuration, an…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-4vg5-rp28-gvjf
- Revision 1 · created ·
Published from osv record GHSA-4vg5-rp28-gvjf
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-44567 Advisory: Open WebUI has Improper Authorization Control IDs: CVE-2026-44567, GHSA-4vg5-rp28-gvjf Record: https://patchnext.com/advisories/cve-2026-44567 (revision 2, source checked 26 Oct 2026, 13:41 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: open-webui 0.1.124. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI open-webui: affected <= 0.1.123; fixed in 0.1.124 ## Suggested inspection (read-only) - `python -m pip show open-webui`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on open-webui. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-4vg5-rp28-gvjf (OSV record GHSA-4vg5-rp28-gvjf lists affected ranges: PyPI open-webui >=0 <0.1.124 (fixed)) - Verified: https://github.com/advisories/GHSA-4vg5-rp28-gvjf (GitHub-reviewed advisory GHSA-4vg5-rp28-gvjf lists affected ranges: PyPI open-webui >=0 <=0.1.123) Commands are suggestions: review each one before running it.
Loading voting…