Quick answers
- Is CVE-2026-45672 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45672 being exploited in the wild.
- How severe is CVE-2026-45672?
- High severity, with a CVSS score of 8.8, published 15 May 2026.
- Which products and versions are affected?
- open-webui (PyPI) <= 0.8.11, ECOSYSTEM:introduced=0,fixed=0.8.12.
- Is there a fix for CVE-2026-45672?
- Yes. open-webui (PyPI): upgrade to 0.8.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45672 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45672?
- Check whether you run open-webui (PyPI) 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 (PyPI): upgrade to 0.8.12 or later
pip install "open-webui>=0.8.12"
Technical details
An incorrect authorization vulnerability (CWE-863) exists in Open WebUI where the `/api/v1/utils/code/execute` endpoint fails to verify the `ENABLE_CODE_EXECUTION` configuration setting. An authenticated user can bypass the administrative 'disabled' state by sending a direct POST request to the execution router. This allows for arbitrary Python code execution within the Jupyter container, which can be leveraged for local file inclusion, process spawning, and Server-Side Request Forgery (SSRF) against internal network services. The issue was resolved in version 0.8.12 by adding a configuration check in the backend router.
Affected products
- Open WebUI Open WebUI <= 0.8.11
Identifiers
- CVE-2026-45672
- GHSA-482j-2pq6-q5w4
- PYSEC-2026-2698
Timeline
- 2026-03-25: other: Vulnerability verified by researcher
- 2026-05-11: patched: Fix released in version 0.8.12
- 2026-05-14: advisory