Quick answers
- Is CVE-2026-45395 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45395 being exploited in the wild.
- How severe is CVE-2026-45395?
- High severity, with a CVSS score of 7.2, published 15 May 2026.
- Which products and versions are affected?
- open-webui (npm) SEMVER:introduced=0,fixed=0.9.5.
- Is there a fix for CVE-2026-45395?
- Yes. open-webui (npm): upgrade to 0.9.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45395 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45395?
- Check whether you run open-webui (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- open-webui (npm): upgrade to 0.9.5 or later
npm install open-webui@0.9.5
Technical details
The vulnerability exists in the `update_tools_by_id` function within `backend/open_webui/routers/tools.py`. While the tool creation endpoint correctly enforces the `workspace.tools` permission, the update endpoint (`POST /api/v1/tools/id/{id}/update`) only verifies if the user is the owner or has a 'write' access grant. Because updating a tool triggers the `exec()` sink to load Python content, an attacker with 'write' access can replace the tool's content with malicious Python code. This results in Remote Code Execution (RCE) as the user running the application (often root in Docker environments), bypassing the intended security boundary where only trusted users should manage tools. The issue is fixed in version 0.9.5.
Affected products
- Open WebUI Open WebUI < 0.9.5
Identifiers
- CVE-2026-45395
- GHSA-p4fx-23fq-jfg6
Timeline
- 2026-05-14: advisory: GitHub Advisory published
- 2026-05-14: patched: Fixed in version 0.9.5