UTC
High

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

CVE-2026-45395 · GHSA-p4fx-23fq-jfg6 · published 2026-05-14 · updated 2026-05-15

Severity
High
CVSS score
7.2
Chance of exploitation (EPSS)
0.44%
Fixed in
0.9.5
  • Exploitation Public proof of concept
  • Automatable No
  • Technical impact Total
  • CISA SSVC
What it is

An attacker with a regular user account and a write access grant on any single tool can: Execute arbitrary server-side code as root (PID 1 in the default Docker deployment) Read sensitive environment variables (WEBUI_SECRET_KEY, OPENAI_API_KEY, etc.) Read/write the application database (all users' chats, files, API keys) Read arbitrary files from the container filesystem Make outbound network requests to internal services The attacker never needs workspace.tools permission. The administrator's explicit decision to deny this user code execution capability is bypassed.

What to do

Upgrade open-webui to 0.9.5 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

File: backend/open_webui/routers/tools.py, lines 451-485 The write access grant is a collaboration primitive used across the application (knowledge bases, prompts, models, tools) for content editing. On every other resource type, a write grant allows editing metadata and content. On tools specifically, because the update endpoint triggers exec(), a write grant silently escalates to code execution but only because the workspace.tools check is missing. If the check were present (as it is on create), the write grant would not confer execution privilege. …

Affected
PackageRegistryAffectedFixed in
open-webuinpm< 0.9.50.9.5

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].