Open WebUI's Ollama Model Access Control Bypass via /api/generate, /api/embed, /api/embeddings, and /api/show
CVE-2026-44563GHSA-rcvp-6fgw-c7fh
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (open-webui 0.9.0), 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.8.12
- Fixed in
- 0.9.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-rcvp-6fgw-c7fh lists affected ranges: PyPI open-webui >=0 <0.9.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-rcvp-6fgw-c7fh lists affected ranges: PyPI open-webui >=0 <=0.8.12
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
- 5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L
- EPSS
- CVE-2026-44563: 0.24% estimated exploitation activity in the next 30 days; percentile 14.89 (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.
Ollama Model Access Control Bypass via /api/generate, /api/embed, /api/embeddings, and /api/show Affected Component Ollama proxy endpoints missing model access control: - backend/openwebui/routers/ollama.py (lines 955-995, generatecompletion) - backend/openwebui/routers/ollama.py (lines 835-881, embed) - backend/openwebui/routers/ollama.py (lines 891-937, embeddings) - backend/openwebui/routers/ollama.py (lines 791-820, showmodelinfo) Affected Versions Current main branch (commit 6fdd19bf1) and likely all versions with Ollama model access control support. Description Four Ollama proxy endpoints accept any model name from the user and forward the request to the Ollama backend without checking whether the user is authorized to access that model. These endpoints only require getverifieduser (any authenticated non-pending user) and validate that the model exists in the full unfiltered model list, but never check AccessGrants.hasaccess(). This is in direct contrast with the…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-rcvp-6fgw-c7fh
- Revision 1 · created ·
Published from osv record GHSA-rcvp-6fgw-c7fh
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-44563 Advisory: Open WebUI's Ollama Model Access Control Bypass via /api/generate, /api/embed, /api/embeddings, and /api/show IDs: CVE-2026-44563, GHSA-rcvp-6fgw-c7fh Record: https://patchnext.com/advisories/cve-2026-44563 (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: Medium (CVSS 5.4) 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.9.0. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI open-webui: affected <= 0.8.12; fixed in 0.9.0 ## 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-rcvp-6fgw-c7fh (OSV record GHSA-rcvp-6fgw-c7fh lists affected ranges: PyPI open-webui >=0 <0.9.0 (fixed)) - Verified: https://github.com/advisories/GHSA-rcvp-6fgw-c7fh (GitHub-reviewed advisory GHSA-rcvp-6fgw-c7fh lists affected ranges: PyPI open-webui >=0 <=0.8.12) Commands are suggestions: review each one before running it.
Loading voting…