Vulnerability in open-webui (CVE-2026-45398)
Summary
Vulnerability in open-webui (CVE-2026-45398). Successful exploitation can lead to full system takeover. Exploitable via POST /api/v1/retrieval/query/doc. Mitigation: upgrade to 0.9.5 or later.
Original description
The description as published by the source.
Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.9.5, _validate_collection_access() checks the user-memory-* and file-* collection name prefixes but does not check knowledge base collections, which use raw UUIDs as collection names. Any authenticated user who knows a private knowledge base UUID can read its content through the retrieval query endpoints, even though the knowledge API correctly denies that user access. The same gap affects the retrieval write endpoints (/process/text, /process/file, /process/files/batch, /process/web, /process/youtube), allowing an attacker to inject content into or overwrite another user's knowledge base. This vulnerability is fixed in 0.9.5.
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-45398 has been found in open-webui.
Attackers can target a specific entry point like POST /api/v1/retrieval/query/doc over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade open-webui to 0.9.5 or later.
If unsure, ask your IT team or search "open-webui CVE-2026-45398" on the vendor's site.
CVE-2026-45398 (open-webui) — CWE-639 / CVSS v3 7.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/retrieval/query/doc / POST /api/v1/retrieval/query/collection / POST /api/v1/retrieval/process/text / POST /api/v1/retrieval/process/file
Patched: 0.9.5 — 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-639) exists in open-webui. Attackers reach the vulnerable code path via POST /api/v1/retrieval/query/doc.
Check the vendor advisory for the affected versions of open-webui. Attack surface: POST /api/v1/retrieval/query/doc / POST /api/v1/retrieval/query/collection / POST /api/v1/retrieval/process/text / POST /api/v1/retrieval/process/file.
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.
Update to 0.9.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/v1/retrieval/query/doc 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 'POST /api/v1/retrieval/query/doc' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/retrieval/query/docへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade open-webui to 0.9.5ステージング環境で 0.9.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/v1/retrieval/query/doc on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com