← Back
CVE-2026-54017
high
CVSS 7.7
Path Traversal in open-webui (CVE-2026-54017)
Summary
path traversal in open-webui (CVE-2026-54017). Confidential information can be exposed externally. Exploitable via `GET /api/v1/terminals/server1/..`. Mitigation: upgrade to `0.9.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54017** has been found in open-webui.
Attackers can target a specific entry point like `GET /api/v1/terminals/server1/..` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade open-webui to **0.9.6** or later.
If unsure, ask your IT team or search "open-webui CVE-2026-54017" on the vendor's site.
CVE-2026-54017 (open-webui) — CWE-22 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/terminals/server1/.. / GET /api/v1/terminals/server1/ / `path` / `_sanitize_proxy_path`
Patched: `0.9.6` — apply immediately
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.
❓ What is the problem
**Path traversal** (CWE-22) exists in open-webui. Attackers reach the vulnerable code path via `GET /api/v1/terminals/server1/..` without authentication.
📍 Affected scope
open-webui — . Attack surface: GET /api/v1/terminals/server1/.. / GET /api/v1/terminals/server1/ / `path` / `_sanitize_proxy_path`.
🔥 Severity
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.9.6**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `GET /api/v1/terminals/server1/..` requests with malformed payloads or SQL meta-characters. Run `grep -r 'open-webui' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'open-webui' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `open-webui` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /api/v1/terminals/server1/..' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /api/v1/terminals/server1/..` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade open-webui to 0.9.6ステージング環境で 0.9.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /api/v1/terminals/server1/.. on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
open-webui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.9.6"}]}]