Vulnerability in open-webui (CVE-2026-54015)
Summary
Vulnerability in open-webui (CVE-2026-54015). Confidential information can be exposed externally. Exploitable via GET /api/v1/prompts/id/{prompt_id}/history/diff. Mitigation: upgrade to 0.9.6 or later.
Original description
The description as published by the source.
Summary
Open WebUI's prompt version-history endpoints authorize the prompt_id in the URL but then act on caller-supplied history IDs without verifying that the history row belongs to that prompt (history_entry.prompt_id == prompt.id). Three operations are affected:
GET /api/v1/prompts/id/{prompt_id}/history/diff— returns another prompt's history snapshots (read).POST /api/v1/prompts/id/{prompt_id}/update/version— restores another prompt's snapshot into the caller's prompt, exposing its content (read).DELETE /api/v1/prompts/id/{prompt_id}/history/{history_id}— deletes another prompt's history entry (delete).
An authenticated user with access to any prompt they control, plus a victim prompt_history.id, can read or delete another user's private prompt history. The single-entry read endpoint (GET .../history/{history_id}) already enforces the binding; these three did not.
Impact
Security boundary crossed: prompt confidentiality and integrity.
Prompt history snapshots can contain private prompt text, internal instructions, and sensitive variables. With a known victim prompt_history.id, an attacker can read another user's snapshot (via the diff endpoint or by restoring it into their own prompt) and delete another user's history entry. The active prompt row is not destroyed; the delete impact is against version history. Exploitation requires knowing or obtaining victim history UUIDs, so severity depends on adjacent ID exposure.
Root Cause…
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-54015 has been found in open-webui.
Attackers can target a specific entry point like GET /api/v1/prompts/id/{prompt_id}/history/diff over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.4/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-54015" on the vendor's site.
CVE-2026-54015 (open-webui) — CWE-284 / CVSS v3 6.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/prompts/id/{prompt_id}/history/diff / POST /api/v1/prompts/id/{prompt_id}/update/version / DELETE /api/v1/prompts/id/{prompt_id}/history/{history_id} / GET /api/v1/prompts/id/ATTACKER_PROMPT_ID/history/diff
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.
A vulnerability (CWE-284) exists in open-webui. Attackers reach the vulnerable code path via GET /api/v1/prompts/id/{prompt_id}/history/diff.
Check the vendor advisory for the affected versions of open-webui. Attack surface: GET /api/v1/prompts/id/{prompt_id}/history/diff / POST /api/v1/prompts/id/{prompt_id}/update/version / DELETE /api/v1/prompts/id/{prompt_id}/history/{history_id} / GET /api/v1/prompts/id/ATTACKER_PROMPT_ID/history/diff.
Severity: Medium (CVSS 6.4/10). Confidential information can be exposed externally.
Update to 0.9.6.
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/prompts/id/{prompt_id}/history/diff 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
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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v1/prompts/id/{prompt_id}/history/diff' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/prompts/id/{prompt_id}/history/diffへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade open-webui to 0.9.6ステージング環境で 0.9.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v1/prompts/id/{prompt_id}/history/diff on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web pypi.org