CVE-2026-70488: Open WebUI: Deletion of directories and file embeddings in other knowledge bases via sync cleanup
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 knowledgefile 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-<id> collection for any file id, breaking chat-with-file for that document. The stored files and their database rows survive, since that path was gated on file ownership, and an owner can restore the state by re-adding and reprocessing. Nothing about the target knowledge base's contents is disclosed to the attacker.
Fix Fixed in https://github.com/open-webui/open-webui/pull/26722. Both request-body loops are now scoped to the knowledge base in the URL: a directory is resolved and skipped unless its knowledgeid matches, and the per-file vector cleanup runs only for files that are members of that knowledge base. Upgrading fully resolves the issue.
Root cause Affected component: backend/openwebui/routers/knowledge.py, handler syncknowledgecleanup, endpoint POST /api/v1/knowledge/{id}/sync/cleanup. Affected setup: all builds from 0.9.6 onward, no optional dependency involved.
The handler treated the write-access check on the URL knowledge base as authorization for everything it went on to do, but the objects it acted on came from the request body and were addressed by primary key alone. Directory deletion at the model layer deletes by directory id and has no notion of a parent knowledge base, so the only thing that could have bound the two together was a membership check in the handler, and there was none. The explicit directory-delete endpoint in the same router already carried that check, which is what makes this a gap in one handler rather than a missing model-layer control.
Credits Reported by @whyiug.
Other sources
Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.9.6 until 0.11.0, the sync cleanup endpoint authorized write access to the knowledge base in the URL but then acted on directory and file ids supplied in the request body without checking that those objects belonged to that knowledge base. A user with write access to one knowledge base could delete directories and remove file embeddings from another knowledge base, causing documents to drop out of retrieval results and breaking chat-with-file for targeted documents without disclosing contents. This issue is fixed in 0.11.0.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/open-webuito a version that resolves this vulnerability.Fixed in 0.11.0 - Upgrade
Upgrade
open-webuito a version that resolves this vulnerability.Fixed in 0.11.0 - Configuration
Update sync_knowledge_cleanup so directory deletion skips any directory whose knowledge_id does not match the knowledge base id from POST /api/v1/knowledge/{id}/sync/cleanup, and so the per-file vector cleanup only runs for files that are members of that same knowledge base (do not act on directory/file ids from request body without verifying ownership by the URL knowledge base).
backend/open_webui/routers/knowledge.py (sync_knowledge_cleanup) scope request-body cleanup loops to knowledge base in URL = knowledge_id must match resolved directory knowledge_id; per-file vector cleanup runs only for files that are members of that knowledge base - Compensating control
If you have knowledge bases shared with non-admin users, ensure only intended owners/collaborators have write access, since the attacker requires write access to at least one knowledge base to exploit the sync cleanup authorization gap.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-70488?
CVE-2026-70488 has a medium severity rating of 4.3.
How do I fix CVE-2026-70488?
To mitigate CVE-2026-70488, update your Open WebUI installation to the latest version that addresses this vulnerability.
What type of access is required to exploit CVE-2026-70488?
An attacker needs write access to at least one knowledge base to exploit CVE-2026-70488.
What can an attacker do with CVE-2026-70488?
An attacker can delete directories and drop file embeddings in knowledge bases that they do not control.
When was CVE-2026-70488 published?
CVE-2026-70488 was published on August 4, 2026.