Open WebUI: Jupyter code execution works despite `ENABLE_CODE_EXECUTION=false` — feature gate bypassed
Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.8.12, the /api/v1/utils/code/execute endpoint executes arbitrary Python code via Jupyter for any verified user, even when the admin has set ENABLE_CODE_EXECUTION=false. The feature gate is not enforced on the API endpoint — the configuration says "disabled" but code still executes. This vulnerability is fixed in 0.8.12.
- Published
- May 15, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 46th percentile
- CWE
- CWE-863
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| openwebui | open webui | cpe:2.3:a:openwebui:open_webui |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openwebui open webuibefore 0.8.12
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
open-webui open-webui
- < 0.8.12affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| PyPI | open-webui | before 0.8.12 | 0.8.12 |
Same product
openwebui: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-44566Open WebUI: Arbitrary File Upload and Path Traversal39Monitor
- CVE-2026-56400open-webui - Remote Code Execution via CORS Misconfiguration and Session Validation36Monitor
- CVE-2026-59216Open WebUI: Cross-user code-interpreter and tool execution via unvalidated Socket.IO event-caller session_id36Monitor
- CVE-2026-59214Open WebUI: Stored web worker XSS via Pyodide36Monitor
- CVE-2026-44551Open WebUI: LDAP Empty Password Authentication Bypass36Monitor
- CVE-2024-8017Cross-site Scripting (XSS) in open-webui/open-webui36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| open-webui open-webui | 0.8.12 · description | Vendor (CNA) |
| PyPI:open-webui | 0.8.12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-453390 days apartOpen WebUI: API key endpoint restrictions bypassed via `x-api-key` header — full message processing on restricted endpoints26Monitor
- CVE-2026-88005118 days apartOpen WebUI: Users denied by the OAuth domain allowlist or role policy can still sign in via token exchange26Monitor
- CVE-2026-88006118 days apartOpen WebUI: Users denied by the OAuth role policy can still sign in via token exchange26Monitor
- CVE-2026-5402139 days apartOpen WebUI: Authenticated users can target arbitrary configured Ollama backends via unguarded url_idx path parameter25Monitor
- CVE-2026-7049081 days apartOpen WebUI: Unapproved accounts can open terminal sessions via a WebSocket auth path missing the role check25Monitor
- CVE-2026-445640 days apartOpen WebUI: Read-Only Users Can Modify Collaborative Documents via Socket.IO21Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →