Vulnerability in open-webui (CVE-2026-44560)
Summary
Vulnerability in open-webui (CVE-2026-44560). Confidential information can be exposed externally. Exploitable via POST /api/chat/completions. Mitigation: upgrade to 0.9.0 or later.
Original description
The description as published by the source.
Unauthorized File and Knowledge Base Content Access via RAG Vector Search
Affected Component
RAG source resolution in chat completion pipeline:
backend/open_webui/retrieval/utils.py(lines 963-965, 1063-1068, 1126-1131 inget_sources_from_items)
Affected Versions
Current main branch (commit 6fdd19bf1) and likely all versions with RAG functionality.
Description
The get_sources_from_items function resolves file and knowledge base references into vector search queries during chat completion. Three of the five code paths perform vector store queries without any authorization check, allowing users to extract content from files and knowledge bases they do not have access to.
| Path | Lines | Access Check |
|---|---|---|
type: "file", full-context |
1044-1050 | ✅ has_access_to_file |
type: "file", non-full-context (default) |
1063-1068 | ❌ None |
type: "collection" |
1070-1118 | ✅ Present |
type: "text" with collection_name |
963-965 | ❌ None |
Bare collection_name/collection_names |
1126-1131 | ❌ None |
The three unprotected paths pass user-supplied collection names directly to query_collection(), which queries the vector store without any authorization. Collection names follow predictable formats: file- for files and the knowledge base UUID for knowledge bases.
CVSS 3.1 Breakdown
| Metric | Value | Rationale |
|---|---|---|
| Attack Vector | Network (N) | Exploited remotely via c… |
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-44560 has been found in open-webui.
Attackers can target a specific entry point like POST /api/chat/completions over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade open-webui to 0.9.0 or later.
If unsure, ask your IT team or search "open-webui CVE-2026-44560" on the vendor's site.
CVE-2026-44560 (open-webui) — CWE-862 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/chat/completions / get_sources_from_items / has_access_to_file / collection_name
Patched: 0.9.0 — 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-862) exists in open-webui. Attackers reach the vulnerable code path via POST /api/chat/completions.
Check the vendor advisory for the affected versions of open-webui. Attack surface: POST /api/chat/completions / get_sources_from_items / has_access_to_file / collection_name.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 0.9.0.
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/chat/completions 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/chat/completions' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/chat/completionsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade open-webui to 0.9.0ステージング環境で 0.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/chat/completions on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com