Information Disclosure in Open WebUI (CVE-2026-109293)
Summary
Vulnerability in Open WebUI (CVE-2026-109293). Confidential information can be exposed externally. Exploitable via GET /api/v1/tools/export.
Original description
The description as published by the source.
Open WebUI from 0.11.0 before 0.11.4 contains an information disclosure vulnerability that allows authenticated non-admin users with tool export permission to obtain tool source code shared with them read-only. Attackers can request GET /api/v1/tools/export to retrieve the full Python source of read-only shared tools, exposing embedded API keys and credentials.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-109293 has been found in Open WebUI.
Attackers can target a specific entry point like GET /api/v1/tools/export over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Open WebUI CVE-2026-109293" on the vendor's site.
CVE-2026-109293 (Open WebUI) — CWE-200 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/tools/export
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in Open WebUI. Attackers reach the vulnerable code path via GET /api/v1/tools/export.
Check the vendor advisory for the affected versions of Open WebUI. Attack surface: GET /api/v1/tools/export.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/v1/tools/export requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Open WebUI を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'GET /api/v1/tools/export' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/tools/exportへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /api/v1/tools/export on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web github.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com