<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 23 Oct 2026 23:37:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-26193 — Open WebUI vulnerable to Stored XSS via iFrame embeds in response messages</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-26193</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; open-webui&lt;/p&gt;
&lt;p&gt;Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to version 0.6.44, aanually modifying chat history allows setting the `embeds` property on a response message, the content of which is loaded into an iFrame with a sandbox that has `allow-scripts` and `allow-same-origin` set, ignoring the &amp;#34;iframe Sandbox Allow Same Origin&amp;#34; configuration. This enables stored XSS on the affected chat. This also triggers when the chat is in the shared format. The result is a shareable link containing the payload that can be distributed to any other users on the instance. Version 0.6.44 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; open-webui&lt;/p&gt;
&lt;p&gt;Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to version 0.6.44, aanually modifying chat history allows setting the `embeds` property on a response message, the content of which is loaded into an iFrame with a sandbox that has `allow-scripts` and `allow-same-origin` set, ignoring the &amp;#34;iframe Sandbox Allow Same Origin&amp;#34; configuration. This enables stored XSS on the affected chat. This also triggers when the chat is in the shared format. The result is a shareable link containing the payload that can be distributed to any other users on the instance. Version 0.6.44 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-26193</guid>
    </item>
    <item>
      <title>PYSEC-2026-2760 — Open WebUI vulnerable to Stored XSS via iFrame embeds in response messages</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-2760</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: open-webui&lt;/p&gt;
&lt;p&gt;### Summary
Manually modifying chat history allows setting the `embeds` property on a response message, the content of which is loaded into an iFrame with a sandbox that has `allow-scripts` and `allow-same-origin` set, ignoring the &amp;#34;iframe Sandbox Allow Same Origin&amp;#34; configuration. This enables stored XSS on the affected chat. This also triggers when the chat is in the shared format. The result is a shareable link containing the payload that can be distributed to any other users on the instance.&lt;/p&gt;
&lt;p&gt;### Details
The flaw stems from how iFrames are constructed here:
https://github.com/open-webui/open-webui/blob/6f1486ffd0cb288d0e21f41845361924e0d742b3/src/lib/components/chat/Messages/ResponseMessage.svelte#L689-L703&lt;/p&gt;
&lt;p&gt;`messages.embeds` is a user controlled property and so can be arbitrarily set by the user to a payload of their choosing. Since `allowScripts` and `allowSameOrigin` are harcoded as true here the sandboxing offers essentially no protection.&lt;/p&gt;
&lt;p&gt;### PoC
Create an arbitrary chat:
&amp;lt;img width=&amp;#34;2468&amp;#34; height=&amp;#34;1426&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/41e32f5c-3fa7-4208-a71f-85556eec6309&amp;#34; /&amp;gt;
Edit the model response:
&amp;lt;img width=&amp;#34;632&amp;#34; height=&amp;#34;192&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/b1e79303-360f-46e3-8d6d-3309c3ec30af&amp;#34; /&amp;gt;
&amp;lt;img width=&amp;#34;2150&amp;#34; height=&amp;#34;434&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/78f19d7f-10dc-4e91-83cc-2d4811e58496&amp;#34; /&amp;gt;
Before saving, configure the browser to use an HTTP proxy tool (Burp/Caido/ZAP) an…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: open-webui&lt;/p&gt;
&lt;p&gt;### Summary
Manually modifying chat history allows setting the `embeds` property on a response message, the content of which is loaded into an iFrame with a sandbox that has `allow-scripts` and `allow-same-origin` set, ignoring the &amp;#34;iframe Sandbox Allow Same Origin&amp;#34; configuration. This enables stored XSS on the affected chat. This also triggers when the chat is in the shared format. The result is a shareable link containing the payload that can be distributed to any other users on the instance.&lt;/p&gt;
&lt;p&gt;### Details
The flaw stems from how iFrames are constructed here:
https://github.com/open-webui/open-webui/blob/6f1486ffd0cb288d0e21f41845361924e0d742b3/src/lib/components/chat/Messages/ResponseMessage.svelte#L689-L703&lt;/p&gt;
&lt;p&gt;`messages.embeds` is a user controlled property and so can be arbitrarily set by the user to a payload of their choosing. Since `allowScripts` and `allowSameOrigin` are harcoded as true here the sandboxing offers essentially no protection.&lt;/p&gt;
&lt;p&gt;### PoC
Create an arbitrary chat:
&amp;lt;img width=&amp;#34;2468&amp;#34; height=&amp;#34;1426&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/41e32f5c-3fa7-4208-a71f-85556eec6309&amp;#34; /&amp;gt;
Edit the model response:
&amp;lt;img width=&amp;#34;632&amp;#34; height=&amp;#34;192&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/b1e79303-360f-46e3-8d6d-3309c3ec30af&amp;#34; /&amp;gt;
&amp;lt;img width=&amp;#34;2150&amp;#34; height=&amp;#34;434&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/78f19d7f-10dc-4e91-83cc-2d4811e58496&amp;#34; /&amp;gt;
Before saving, configure the browser to use an HTTP proxy tool (Burp/Caido/ZAP) an…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-2760</guid>
    </item>
  </channel>
</rss>
