Categories
CVE-2026-70488 medium CVSS 4.3

Vulnerability in open-webui (CVE-2026-70488)

Summary

Vulnerability in open-webui (CVE-2026-70488). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/v1/knowledge/{id}/sync/cleanup. Mitigation: upgrade to 0.11.0 or later.

Original description

The description as published by the source.

Summary

A user with write access to one knowledge base could delete directories, and drop file embeddings, belonging to knowledge bases they do not control. The sync cleanup endpoint verified write access on the knowledge base named in the URL and then acted on the directory and file ids supplied in the request body without checking that those objects belonged to that knowledge base.

Preconditions

Default configuration, no flags involved. The attacker needs write access to at least one knowledge base, which comes from owning one, from a write access grant, or from the admin role; workspace.knowledge is off by default, so an ordinary user cannot simply create one. They also need the victim's directory or file id, which are UUIDs and are not enumerable, so in practice the attacker is someone who can already see the target knowledge base, typically a read-only collaborator on a shared one. Deployments where no knowledge base is shared beyond its owner are not reachable.

Impact

The attacker deletes a target directory and, because the deletion runs without moving files to the parent, the knowledge_file associations for every file in that subtree are removed as well, so those documents silently drop out of the victim's knowledge base and out of its retrieval results. Separately, the per-file vector cleanup dropped the standalone file- collection for any file id, breaking chat-with-file for that document. The stored files and their database rows survive, since that pa…

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-70488 has been found in open-webui.
Attackers can target a specific entry point like POST /api/v1/knowledge/{id}/sync/cleanup over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade open-webui to 0.11.0 or later.
If unsure, ask your IT team or search "open-webui CVE-2026-70488" on the vendor's site.

CVE-2026-70488 (open-webui) — CWE-639 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/knowledge/{id}/sync/cleanup / workspace.knowledge / knowledge_id / sync_knowledge_cleanup
Patched: 0.11.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.

❓ What is the problem

A vulnerability (CWE-639) exists in open-webui. Attackers reach the vulnerable code path via POST /api/v1/knowledge/{id}/sync/cleanup.

📍 Affected scope

Check the vendor advisory for the affected versions of open-webui. Attack surface: POST /api/v1/knowledge/{id}/sync/cleanup / workspace.knowledge / knowledge_id / sync_knowledge_cleanup.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.11.0.

🛡️ 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 POST /api/v1/knowledge/{id}/sync/cleanup 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

  1. 1
    Identify exposure identify
    grep -r 'open-webui' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で open-webui を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'POST /api/v1/knowledge/{id}/sync/cleanup' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/v1/knowledge/{id}/sync/cleanup への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade open-webui to 0.11.0

    ステージング環境で 0.11.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against POST /api/v1/knowledge/{id}/sync/cleanup on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

pip open-webui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.11.0"}]}]
PyPI open-webui
[{"type":"ECOSYSTEM","events":[{"introduced":"0.9.6"},{"fixed":"0.11.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details