CVE-2026-44555 — open-webui
HIGHCVE-2026-44555 is a high-severity (CVSS 7.6) CWE-862 vulnerability in open-webui. A fix is available for open-webui — see the affected versions and patch details below.
Open WebUI: Base Model Routing Bypasses Access Control via Model Chaining
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-44555.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
open-webuiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Base Model Routing Bypasses Access Control via Model Chaining
Affected Component
Model chaining via base_model_id:
backend/open_webui/routers/models.py(lines 170-214,create_new_model)backend/open_webui/routers/models.py(lines 254-308,import_models)backend/open_webui/main.py(lines 1696-1711, base model resolution in chat completion)backend/open_webui/routers/openai.py(lines 1032-1037, base model payload rewrite)backend/open_webui/routers/ollama.py(lines 1086-1090, base model payload rewrite)backend/open_webui/utils/models.py(line 380,check_model_access— checks user-facing model only)
Affected Versions
Current main branch (commit 6fdd19bf1) and likely all versions with the model chaining (base_model_id) feature.
Description
Open WebUI supports model composition via base_model_id: a user-defined model (e.g., "Cheap Assistant") can reference an existing base model (e.g., "gpt-4-turbo-restricted") that provides the actual inference capability. When a user queries the composed model, the access control pipeline verifies the user has access to the composed model but never re-verifies access to the chained base model.
Additionally, the model creation and import endpoints accept arbitrary base_model_id values without checking that the caller has access to that base model. Combined, this allows any user with the default model creation permission to create a model that chains to a restricted base model — and then invoke it, causing the server to dispatch the request to the restricted base model using the admin-configured API key.
# utils/models.py:380 — access check runs against the user-facing model only
def check_model_access(user, model):
if user.role == 'user':
...check access grants on `model`...
# main.py:1696-1711 — base model resolved without access check
base_model = request.app.state.MODELS.get(model.info.base_model_id)
if base_model:
# payload["model"] is rewritten to base_model.id
# but no check_model_access(user, base_model) is performed
# openai.py:1032-1037 / ollama.py:1086-1090 — the rewritten payload is dispatched
payload['model'] = base_model_id
Attack Scenario
- Admin provisions a premium/restricted model
gpt-4-turbo-restrictedand configures access grants so only the "ML Engineers" group can use it. - Attacker (a regular user not in that group) calls:
The creation endpoint does not validate the attacker's access toPOST /api/v1/models/create { "id": "cheap-assistant", "name": "Cheap Assistant", "base_model_id": "gpt-4-turbo-restricted", "params": {}, "meta": {} }gpt-4-turbo-restricted. - Attacker now owns
cheap-assistant.check_model_access(attacker, cheap-assistant)passes trivially because they are the owner. - Attacker sends:
POST /api/chat/completions {"model": "cheap-assistant", "messages": [...]} - At
main.py:1696, the pipeline resolvescheap-assistant.base_model_idtogpt-4-turbo-restricted, rewritespayload["model"]to the base model ID, and dispatches the upstream request with the admin-configured API key for the backend. - The attacker receives responses from the restricted model, bypassing the access grant policy.
The same bypass is available via the import endpoint, which additionally allows overwriting existing models (see related finding on model import ownership).
Impact
- Regular users can query restricted models by chaining through a self-owned wrapper model
- Access control on
gpt-4-turbo-restricted(or equivalent paid/tiered/internal models) becomes silently ineffective - Direct cost impact on pay-per-token backends (OpenAI, Anthropic, Azure) — the admin's API key is used for requests the admin intended to forbid
- Creates a false sense of security — the admin sees access restrictions work through the standard model selector but not through user-created chains
Preconditions
- Attacker must have model creation permission (default
workspace.modelspermission, granted to all users by default) - A restricted base model must exist on the instance (the target of the chain)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | open-webui | all versions | 0.9.0pip install --upgrade 'open-webui==0.9.0' |
Affected Products
open webuiopenwebuiDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for open-webui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update open-webui to 0.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44555 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-44555 in your dependencies?
Find it across PyPI, including transitive dependencies.