← Back
GHSA-6xcp-7mpr-m7wm
Vulnerability in open-webui (GHSA-6xcp-7mpr-m7wm)
Summary
vulnerability in open-webui (GHSA-6xcp-7mpr-m7wm). Successful exploitation can lead to full system takeover. Exploitable via ``attacker.com``. Mitigation: upgrade to `0.3.33` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-6xcp-7mpr-m7wm** has been found in open-webui.
Attackers can target a specific entry point like ``attacker.com`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade open-webui to **0.3.33** or later.
If unsure, ask your IT team or search "open-webui GHSA-6xcp-7mpr-m7wm" on the vendor's site.
GHSA-6xcp-7mpr-m7wm (open-webui) — CWE-613 /
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `attacker.com` / `whoami`
Patched: `0.3.33` — 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
**A vulnerability** (CWE-613) exists in open-webui. Attackers reach the vulnerable code path via ``attacker.com`` without authentication.
📍 Affected scope
open-webui — . Attack surface: `attacker.com` / `whoami`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.3.33**.
🛡️ 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 request patterns matching this CVE's known IOCs. 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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade open-webui to 0.3.33ステージング環境で 0.3.33 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
open-webui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.33"}]}]
PyPI
open-webui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.33"}]}]