dbcve.org
Open WebuiApplication · Openwebui

CVE-2026-54021

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 0.9.6 or later.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.9.6, several direct, index-addressed Ollama proxy routes accept a caller-supplied url_idx path parameter and use it as a raw index into the admin-configured OLLAMA_BASE_URLS list. Access control on these routes validates only whether the user may use the requested model, never which backend the request is routed to. Any authenticated user can append an arbitrary url_idx to force their request onto an Ollama backend they were never authorized to reach, including internal, higher-privilege, or explicitly admin-disabled backends. This vulnerability is fixed in 0.9.6.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Open WebUI prior to 0.9.6 contains an index-based authorization bypass in Ollama proxy routes. The url_idx path parameter is used directly to index into the admin-configured OLLAMA_BASE_URLS list without validating user authorization for that specific backend. Any authenticated user can manipulate this parameter to access Ollama backends they were never authorized to reach, including internal or admin-disabled backends.

MitigationUpgrade to Open WebUI version 0.9.6 or later, which implements proper authorization validation on the url_idx parameter before routing requests to Ollama backends.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Open WebuiApplication
Affected:< 0.9.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Open WebUI version
    Check the installed version of Open WebUI by reviewing the package metadata, container image tag, or the running application's version display. Compare against the affected range: versions prior to 0.9.6 are vulnerable.
    Affected if The installed version is less than 0.9.6
  2. Confirm Ollama integration is configured
    Locate the Open WebUI configuration that defines OLLAMA_BASE_URLS. This is typically an environment variable or configuration file that lists multiple Ollama backend URLs.
    Affected if OLLAMA_BASE_URLS contains more than one backend URL (multiple Ollama instances)
  3. Verify proxy route accessibility
    Determine if authenticated users can access the Ollama proxy endpoints that accept the url_idx path parameter. These routes typically follow a pattern such as /ollama/v1/chat or /api/ollama/ with an index parameter.
    Affected if The proxy routes are exposed to authenticated (non-admin) users without additional authorization checks on the url_idx parameter

You are affected if Open WebUI version is below 0.9.6 AND multiple Ollama backends are configured in OLLAMA_BASE_URLs, allowing any authenticated user to bypass authorization by manipulating the url_idx parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.9.6 or later
Fixed in 0.9.6
Interim mitigation

Upgrade to Open WebUI version 0.9.6 or later, which implements proper authorization validation on the url_idx parameter before routing requests to Ollama backends.

Recommended fix High confidence

0.9.6

  1. 1. Back up your current Open WebUI configuration and data directory
  2. 2. Upgrade Open WebUI to version 0.9.6 or later (e.g., docker pull ghcr.io/open-webui/open-webui:main or pip install open-webui==0.9.6)
  3. 3. Restart the Open WebUI service
  4. 4. Verify the upgrade was successful by checking the version number in the UI or via API
  5. 5. Test that the url_idx parameter is now properly validated and unauthorized backends cannot be accessed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Open Webui Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54021 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54021 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data