<?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>Tue, 13 Oct 2026 04:06:16 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-07133</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-07133</link>
      <description>bdu:2026-07133</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-07133</guid>
    </item>
    <item>
      <title>EUVD-2026-319084</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-319084</link>
      <description>EUVD-2026-319084</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-319084</guid>
    </item>
    <item>
      <title>fkie_cve-2026-45387</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-45387</link>
      <description>&lt;p&gt;Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.9.5, when setting model permissions so that a group has read access to it, intending for other users to use it, those users also can read the model&amp;#39;s system prompt. However users may consider their system prompt confidential, so this is considered a security issue. This vulnerability is fixed in 0.9.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.9.5, when setting model permissions so that a group has read access to it, intending for other users to use it, those users also can read the model&amp;#39;s system prompt. However users may consider their system prompt confidential, so this is considered a security issue. This vulnerability is fixed in 0.9.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-45387</guid>
    </item>
    <item>
      <title>GHSA-h2cw-7qw9-56xr — Open WebUI: Sharing models for others to use (read permission) also exposes model details (system prompt leakage)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h2cw-7qw9-56xr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: open-webui&lt;/p&gt;
&lt;p&gt;### Summary
When setting model permissions so that a group has read access to it, intending for other users to use it, those users also can read the model&amp;#39;s system prompt.&lt;/p&gt;
&lt;p&gt;However users may consider their system prompt confidential, so we consider this a security issue.&lt;/p&gt;
&lt;p&gt;Compare https://genai.owasp.org/llmrisk/llm072025-system-prompt-leakage/ or prompt injections to get popular chatbots on the internet to reveal their prompt.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;We discovered that users can open the workspace model edit page /workspace/models/edit?id=notmymodel for models that do not appear in their workspace.&lt;/p&gt;
&lt;p&gt;Saving is not possible, that permission check is correct.&lt;/p&gt;
&lt;p&gt;On the API level:&lt;/p&gt;
&lt;p&gt;- ```/api/v1/models/model?id=notmymodel``` -&amp;gt; returns the model details, most importantly params.system
- even though ```/api/v1/models/list``` does NOT contain the model since it checks for write permission.
- ```/api/models``` contains the model correctly and does not reveal the system prompt.&lt;/p&gt;
&lt;p&gt;It seems inconsistent that the REST API list does not contain an item, but if you know the id, you can access it anyway.&lt;/p&gt;
&lt;p&gt;### PoC
- create model
- give read permission to group with another user
- other user can access ```/api/v1/models/model?id=notmymodel```&lt;/p&gt;
&lt;p&gt;### Impact
System prommpt leakage&lt;/p&gt;
&lt;p&gt;If this is intended behavior for the &amp;#34;read&amp;#34; permission, maybe there should be an additional &amp;#34;use&amp;#34; permission (which would be 99% of use cases of the read permission i believe).&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
When setting model permissions so that a group has read access to it, intending for other users to use it, those users also can read the model&amp;#39;s system prompt.&lt;/p&gt;
&lt;p&gt;However users may consider their system prompt confidential, so we consider this a security issue.&lt;/p&gt;
&lt;p&gt;Compare https://genai.owasp.org/llmrisk/llm072025-system-prompt-leakage/ or prompt injections to get popular chatbots on the internet to reveal their prompt.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;We discovered that users can open the workspace model edit page /workspace/models/edit?id=notmymodel for models that do not appear in their workspace.&lt;/p&gt;
&lt;p&gt;Saving is not possible, that permission check is correct.&lt;/p&gt;
&lt;p&gt;On the API level:&lt;/p&gt;
&lt;p&gt;- ```/api/v1/models/model?id=notmymodel``` -&amp;gt; returns the model details, most importantly params.system
- even though ```/api/v1/models/list``` does NOT contain the model since it checks for write permission.
- ```/api/models``` contains the model correctly and does not reveal the system prompt.&lt;/p&gt;
&lt;p&gt;It seems inconsistent that the REST API list does not contain an item, but if you know the id, you can access it anyway.&lt;/p&gt;
&lt;p&gt;### PoC
- create model
- give read permission to group with another user
- other user can access ```/api/v1/models/model?id=notmymodel```&lt;/p&gt;
&lt;p&gt;### Impact
System prommpt leakage&lt;/p&gt;
&lt;p&gt;If this is intended behavior for the &amp;#34;read&amp;#34; permission, maybe there should be an additional &amp;#34;use&amp;#34; permission (which would be 99% of use cases of the read permission i believe).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h2cw-7qw9-56xr</guid>
    </item>
    <item>
      <title>PYSEC-2026-2728 — Open WebUI: Sharing models for others to use (read permission) also exposes model details (system prompt leakage)</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-2728</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: open-webui&lt;/p&gt;
&lt;p&gt;### Summary
When setting model permissions so that a group has read access to it, intending for other users to use it, those users also can read the model&amp;#39;s system prompt.&lt;/p&gt;
&lt;p&gt;However users may consider their system prompt confidential, so we consider this a security issue.&lt;/p&gt;
&lt;p&gt;Compare https://genai.owasp.org/llmrisk/llm072025-system-prompt-leakage/ or prompt injections to get popular chatbots on the internet to reveal their prompt.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;We discovered that users can open the workspace model edit page /workspace/models/edit?id=notmymodel for models that do not appear in their workspace.&lt;/p&gt;
&lt;p&gt;Saving is not possible, that permission check is correct.&lt;/p&gt;
&lt;p&gt;On the API level:&lt;/p&gt;
&lt;p&gt;- ```/api/v1/models/model?id=notmymodel``` -&amp;gt; returns the model details, most importantly params.system
- even though ```/api/v1/models/list``` does NOT contain the model since it checks for write permission.
- ```/api/models``` contains the model correctly and does not reveal the system prompt.&lt;/p&gt;
&lt;p&gt;It seems inconsistent that the REST API list does not contain an item, but if you know the id, you can access it anyway.&lt;/p&gt;
&lt;p&gt;### PoC
- create model
- give read permission to group with another user
- other user can access ```/api/v1/models/model?id=notmymodel```&lt;/p&gt;
&lt;p&gt;### Impact
System prommpt leakage&lt;/p&gt;
&lt;p&gt;If this is intended behavior for the &amp;#34;read&amp;#34; permission, maybe there should be an additional &amp;#34;use&amp;#34; permission (which would be 99% of use cases of the read permission i believe).&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
When setting model permissions so that a group has read access to it, intending for other users to use it, those users also can read the model&amp;#39;s system prompt.&lt;/p&gt;
&lt;p&gt;However users may consider their system prompt confidential, so we consider this a security issue.&lt;/p&gt;
&lt;p&gt;Compare https://genai.owasp.org/llmrisk/llm072025-system-prompt-leakage/ or prompt injections to get popular chatbots on the internet to reveal their prompt.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;We discovered that users can open the workspace model edit page /workspace/models/edit?id=notmymodel for models that do not appear in their workspace.&lt;/p&gt;
&lt;p&gt;Saving is not possible, that permission check is correct.&lt;/p&gt;
&lt;p&gt;On the API level:&lt;/p&gt;
&lt;p&gt;- ```/api/v1/models/model?id=notmymodel``` -&amp;gt; returns the model details, most importantly params.system
- even though ```/api/v1/models/list``` does NOT contain the model since it checks for write permission.
- ```/api/models``` contains the model correctly and does not reveal the system prompt.&lt;/p&gt;
&lt;p&gt;It seems inconsistent that the REST API list does not contain an item, but if you know the id, you can access it anyway.&lt;/p&gt;
&lt;p&gt;### PoC
- create model
- give read permission to group with another user
- other user can access ```/api/v1/models/model?id=notmymodel```&lt;/p&gt;
&lt;p&gt;### Impact
System prommpt leakage&lt;/p&gt;
&lt;p&gt;If this is intended behavior for the &amp;#34;read&amp;#34; permission, maybe there should be an additional &amp;#34;use&amp;#34; permission (which would be 99% of use cases of the read permission i believe).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-2728</guid>
    </item>
  </channel>
</rss>
