Skip to main content
Vulnerability Database/CVE-2026-109293

CVE-2026-109293: Open WebUI Information Disclosure Flaw

CVE-2026-109293 is an information disclosure vulnerability in Open WebUI versions 0.11.0 to 0.11.3 that exposes tool source code containing API keys and credentials to authenticated users. This article covers technical details, affected versions, security impact, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-109293 Overview

CVE-2026-109293 is an information disclosure vulnerability in Open WebUI versions 0.11.0 through 0.11.3. The flaw permits authenticated non-admin users holding tool export permission to retrieve the full Python source of tools shared with them read-only. Attackers invoke the GET /api/v1/tools/export endpoint to extract source files that may contain embedded API keys, service credentials, and other secrets. The weakness is classified as sensitive information exposure [CWE-200]. Open WebUI resolved the issue in version 0.11.4.

Critical Impact

Authenticated users with export permission can harvest API keys and credentials embedded in read-only shared tools, enabling lateral movement into third-party services.

Affected Products

  • Open WebUI 0.11.0
  • Open WebUI versions after 0.11.0 and before 0.11.4
  • Deployments granting tool export permission to non-admin users

Discovery Timeline

  • 2026-10-12 - CVE-2026-109293 published to NVD
  • 2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-109293

Vulnerability Analysis

Open WebUI exposes a tool export API that returns the Python source of user-defined tools. The permission check on GET /api/v1/tools/export only validates that the caller holds the export capability. It does not evaluate whether the requested tool was shared with the caller in a read-only context versus an editable context.

Tools in Open WebUI frequently embed secrets such as API tokens, cloud credentials, and model provider keys directly in their source code. Owners sharing a tool read-only typically expect downstream users to invoke the tool, not read its implementation. The export endpoint collapses that distinction and returns the raw source.

An attacker with a low-privilege account and export permission can enumerate shared tools and request each one. Harvested credentials can then be reused outside Open WebUI against the originating services.

Root Cause

The root cause is missing authorization enforcement on the export endpoint. The handler verifies feature-level permission but omits a per-resource access check that distinguishes read-only shares from full access. This matches the [CWE-200] pattern of exposing resource contents to actors who should not receive them.

Attack Vector

Exploitation requires network access to the Open WebUI instance and valid credentials for an account that has been granted tool export permission. The attacker issues an authenticated GET /api/v1/tools/export request referencing a tool identifier that was shared read-only. The response returns the complete Python source, including any hardcoded secrets. No user interaction is required beyond the attacker's own authenticated session.

See the GitHub Security Advisory GHSA-2h26-836q-4jh2 and the Vulncheck Advisory Open WebUI Disclosure for additional technical context.

Detection Methods for CVE-2026-109293

Indicators of Compromise

  • Authenticated GET /api/v1/tools/export requests originating from non-admin accounts.
  • Repeated export requests enumerating multiple tool identifiers within a short time window.
  • Use of harvested API keys from external IP addresses shortly after export activity.

Detection Strategies

  • Review Open WebUI reverse proxy and application logs for /api/v1/tools/export calls, correlating caller role with the owner of each exported tool.
  • Alert when the exporting user does not match the tool owner and the share state is read-only.
  • Baseline normal export volume per user and flag outliers.

Monitoring Recommendations

  • Forward Open WebUI access logs to a central logging platform for retention and query.
  • Monitor downstream services for authentication from the IP ranges or user agents associated with Open WebUI accounts after suspected export activity.
  • Track creation of new accounts that are promptly granted tool export permission.

How to Mitigate CVE-2026-109293

Immediate Actions Required

  • Upgrade Open WebUI to version 0.11.4 or later.
  • Audit which non-admin roles currently hold tool export permission and revoke where not required.
  • Rotate any API keys or credentials that were embedded in tools shared with non-admin users.

Patch Information

The maintainers released a fix in Open WebUI 0.11.4. The patch enforces per-tool authorization on the export endpoint so read-only shares no longer disclose source. Patch and advisory details are available in the GitHub Security Advisory GHSA-2h26-836q-4jh2.

Workarounds

  • Remove tool export permission from all non-admin roles until the upgrade is applied.
  • Unshare tools containing embedded secrets, or move secrets to environment variables or a secrets manager referenced by the tool at runtime.
  • Restrict network access to the Open WebUI management API to trusted operators.
bash
# Verify installed Open WebUI version and upgrade
pip show open-webui | grep -i version
pip install --upgrade "open-webui>=0.11.4"

# Docker deployments
docker pull ghcr.io/open-webui/open-webui:0.11.4
docker stop open-webui && docker rm open-webui
docker run -d --name open-webui -p 3000:8080 \
  -v open-webui:/app/backend/data \
  ghcr.io/open-webui/open-webui:0.11.4

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.