# CVE-2026-45395: Open WebUI: Missing `workspace.tools` Authorization Check on Tool Update Endpoint Allows Privilege Escalation to Code Execution

> Attackers can bypass tool management restrictions to execute arbitrary code by updating tools without proper authorization checks.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 May 2026
- **Updated:** 19 May 2026
- **Also known as:** GHSA-p4fx-23fq-jfg6

## What is CVE-2026-45395?

CVE-2026-45395 is a high-severity missing authorization vulnerability in Openwebui Open Webui, published on 15 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.9.5, the tool update endpoint (POST /api/v1/tools/id/{id}/update) is missing the workspace.tools permission check that is present on the tool create endpoint. This allows a user who has been explicitly denied tool management capabilities ( and who the administrator considers untrusted for code execution ) to replace a tool's server-side Python content and trigger execution, bypassing the intended workspace.tools security boundary. This vulnerability is fixed in 0.9.5.

Weakness: CWE-862 (Missing Authorization), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-45395?

2 open source packages ship an affected version, including open-webui. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `open-webui` | npm | All versions | 0.9.5 |
| `open-webui` | npm | All versions | 0.9.5 |

Products: Openwebui Open Webui.

## How do I fix CVE-2026-45395?

Upgrade open-webui to 0.9.5 or later.

## Is CVE-2026-45395 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45395 exists.

## Other vulnerabilities in Openwebui Open Webui

- [CVE-2026-44551](https://insights.sbomify.com/CVE-2026-44551/): Open WebUI: LDAP Empty Password Authentication Bypass (critical 9.1)
- [CVE-2026-56400](https://insights.sbomify.com/CVE-2026-56400/): open-webui - Remote Code Execution via CORS Misconfiguration and Session Validation (critical 9.0)
- [CVE-2024-8017](https://insights.sbomify.com/CVE-2024-8017/): Cross-site Scripting (XSS) in open-webui/open-webui (critical 9.0)
- [CVE-2026-45672](https://insights.sbomify.com/CVE-2026-45672/): Open WebUI: Jupyter code execution works despite `ENABLE_CODE_EXECUTION=false` — feature gate bypassed (high 8.8)
- [CVE-2026-87995](https://insights.sbomify.com/CVE-2026-87995/): Open WebUI: Same-origin XSS to account takeover via terminal port-preview iframe hardcoding allow-same-origin (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45395 and fix it if it is affected.

What it is: CVE-2026-45395 is a high-severity missing authorization vulnerability in Openwebui Open Webui, published on 15 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45395 exists.

Affected packages and fixed versions:
- open-webui (npm): affected all versions; fixed in 0.9.5
- open-webui (npm): affected all versions; fixed in 0.9.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45395/ (Markdown: https://insights.sbomify.com/CVE-2026-45395/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45395
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45395
- OSV: https://osv.dev/vulnerability/CVE-2026-45395

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45395/
Summaries are generated and may contain mistakes; the official description above is the record.