Vulnerability in open-webui (CVE-2026-56400)
Summary
Vulnerability in open-webui (CVE-2026-56400). Successful exploitation can lead to full system takeover. Exploitable via attacker.com. Mitigation: upgrade to 0.3.33 or later.
Original description
The description as published by the source.
open-webui before 0.3.14 contains a cross-origin resource sharing misconfiguration allowing arbitrary origins with allow_origins=* and authenticated requests to the /api/v1/functions endpoint. Attackers can execute arbitrary code on the openwebui instance by crafting malicious cross-site requests from attacker-controlled websites when an admin user visits them.
Source: GitHub Security Advisories (Global) 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-56400 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: 8.3/10.
What to do: upgrade open-webui to 0.3.33 or later.
If unsure, ask your IT team or search "open-webui CVE-2026-56400" on the vendor's site.
CVE-2026-56400 (open-webui) — CWE-613 / CVSS v3 8.3
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.
A vulnerability (CWE-613) exists in open-webui. Attackers reach the vulnerable code path via attacker.com without authentication.
Check the vendor advisory for the affected versions of open-webui. Attack surface: attacker.com / whoami.
Severity: High (CVSS 8.3/10). Successful exploitation can lead to full system takeover.
Update to 0.3.33.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade open-webui to 0.3.33ステージング環境で 0.3.33 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory vulncheck.com
- advisory github.com
- package github.com
- web github.com