<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cve-2026-45402 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-45402/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 14 May 2026 20:31:27 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-45402/feed.xml" rel="self" type="application/rss+xml"/><item><title>Open WebUI Cross-User File Access Vulnerability (CVE-2026-45402)</title><link>https://feed.craftedsignal.io/briefs/2026-05-open-webui-file-access/</link><pubDate>Thu, 14 May 2026 20:31:27 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-open-webui-file-access/</guid><description>Open WebUI is vulnerable to cross-user file access due to unchecked file_id in Folder Knowledge and Knowledge-Base Attach Endpoints, allowing authenticated users to exfiltrate or overwrite other users' private files given the file UUID (CVE-2026-45402).</description><content:encoded><![CDATA[<p>Open WebUI versions 0.9.4 and earlier are susceptible to a cross-user file access vulnerability. The vulnerability stems from a lack of proper authorization checks when handling user-supplied <code>file_id</code> values in the Folder Knowledge and Knowledge-Base Attach endpoints. An authenticated attacker can exploit this flaw to access and potentially overwrite files belonging to other users by manipulating folder knowledge or attaching malicious files to knowledge bases. The vulnerability was reported on May 14, 2026, and affects systems where Open WebUI is deployed. Exploitation requires knowledge of the victim&rsquo;s file UUID, which, while not directly enumerable, may leak through normal usage patterns, such as chat sources, shared chat citations, URL paths, browser history, and export/share flows.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker authenticates to the Open WebUI application.</li>
<li>The attacker obtains the UUID of a target file belonging to another user through various means, such as shared chats, URL paths, or browser history.</li>
<li>The attacker crafts a POST request to the <code>/api/v1/folders/&lt;attacker_folder_id&gt;/update</code> endpoint (Path 1) or <code>/api/v1/knowledge/&lt;kb_id&gt;/file/add</code> endpoint (Path 2).</li>
<li>In Path 1, the attacker includes a <code>data</code> payload with a <code>files</code> array containing the victim&rsquo;s file UUID, structured as <code>{&quot;data&quot;: {&quot;files&quot;: [{&quot;id&quot;: &quot;&lt;victim_file_id&gt;&quot;, &quot;type&quot;: &quot;file&quot;}]}}</code>.</li>
<li>In Path 2, the attacker provides the victim file UUID as the <code>file_id</code> parameter in the request body: <code>{&quot;file_id&quot;:&quot;$VICTIM_FILE_ID&quot;}</code>.</li>
<li>If exploiting path 2, the attacker creates a new knowledge base using the /api/v1/knowledge/create endpoint.</li>
<li>The server, lacking proper authorization checks on the <code>file_id</code>, attaches the victim&rsquo;s file to the attacker&rsquo;s folder or knowledge base.</li>
<li>The attacker can then access the victim&rsquo;s file content through RAG flows (Path 1) or the <code>/api/v1/files/{id}/content</code> endpoint (Path 2) and, in Path 2, overwrite it using the <code>/api/v1/files/{id}/data/content/update</code> endpoint.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows any authenticated user to read the contents of any other user&rsquo;s private uploaded file, given knowledge of the file UUID. In the case of Path 2 (knowledge-base attach), the attacker can also overwrite the victim&rsquo;s file content, leading to data tampering and potential misinformation. This can lead to unauthorized data access, data breaches, and integrity compromises. There is no direct availability impact, as the file rows are not deleted.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply the recommended fix by validating the supplied file_id against the caller&rsquo;s read access before attaching the file in every writer function (backend/open_webui/routers/folders.py, backend/open_webui/routers/knowledge.py).</li>
<li>Deploy the Sigma rule <code>Detect Open WebUI Knowledge Base File Add</code> to detect exploitation attempts targeting the Knowledge-Base Attach endpoint (Path 2).</li>
<li>Deploy the Sigma rule <code>Detect Open WebUI Folder Update with File Injection</code> to detect exploitation attempts targeting the Folder Knowledge ingestion path (Path 1).</li>
<li>Upgrade to a patched version of Open WebUI that addresses CVE-2026-45402.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>open-webui</category><category>file-access</category><category>privilege-escalation</category><category>cve-2026-45402</category></item></channel></rss>