<?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, 17 Nov 2026 21:35:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-45666 — Open WebUI: Indirect Object Reference (IDOR) in user notes</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-45666</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 0.8.11, the API /api/v1/notes/{note_id} endpoint lacks proper authorization checks, allowing authenticated users to retrieve notes belonging to other users by guessing or enumerating UUIDs. This results in unauthorized disclosure of potentially sensitive or private user data. This vulnerability is fixed in 0.8.11.&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 0.8.11, the API /api/v1/notes/{note_id} endpoint lacks proper authorization checks, allowing authenticated users to retrieve notes belonging to other users by guessing or enumerating UUIDs. This results in unauthorized disclosure of potentially sensitive or private user data. This vulnerability is fixed in 0.8.11.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-45666</guid>
    </item>
    <item>
      <title>PYSEC-2026-2768 — Open WebUI has an Indirect Object Reference (IDOR) in user notes</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-2768</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: open-webui&lt;/p&gt;
&lt;p&gt;### Summary
The  API /api/v1/notes/{note_id} endpoint lacks proper authorization checks, allowing authenticated users to retrieve notes belonging to other users by guessing or enumerating UUIDs. This results in unauthorized disclosure of potentially sensitive or private user data.&lt;/p&gt;
&lt;p&gt;### Details
- if notes is enabled from UI (Settings &amp;gt;&amp;gt; General &amp;gt;&amp;gt; Features &amp;gt;&amp;gt; Notes (Beta))
   - From API, attacker can access other user notes
- if notes is disabled from UI (Settings &amp;gt;&amp;gt; General &amp;gt;&amp;gt; Features &amp;gt;&amp;gt; Notes (Beta))
   - Then attacker can enable the notes from /api/config and access other user notes&lt;/p&gt;
&lt;p&gt;### PoC
- Step 1: Log in to the application as a valid user (User A).
![image](https://github.com/user-attachments/assets/3c4625f9-6e51-4cd1-942e-6a3f467520c0)&lt;/p&gt;
&lt;p&gt;- Step 2: Intercept or inspect the response from the endpoint GET /api/config.
![image](https://github.com/user-attachments/assets/7c4fe716-314c-4640-bc9f-1e11ddc2273d)&lt;/p&gt;
&lt;p&gt;- Step 3: Observe the field &amp;#34;enable_notes&amp;#34;: false in the JSON response.
- Step 4: Manually change &amp;#34;enable_notes&amp;#34; to true using browser DevTools or by intercepting and modifying the response via a proxy like Burp Suite. (Please note, the occurrence of this API comes twice, hence modification needs to be made twice as well.)
![image](https://github.com/user-attachments/assets/99575570-a673-4508-b149-9a2480d8f62e)&lt;/p&gt;
&lt;p&gt;- Step 5: Observe the loaded frontend application; the previously hidden notes form will now be visible.
![image](https://github.com/user-attachments/assets/…&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
The  API /api/v1/notes/{note_id} endpoint lacks proper authorization checks, allowing authenticated users to retrieve notes belonging to other users by guessing or enumerating UUIDs. This results in unauthorized disclosure of potentially sensitive or private user data.&lt;/p&gt;
&lt;p&gt;### Details
- if notes is enabled from UI (Settings &amp;gt;&amp;gt; General &amp;gt;&amp;gt; Features &amp;gt;&amp;gt; Notes (Beta))
   - From API, attacker can access other user notes
- if notes is disabled from UI (Settings &amp;gt;&amp;gt; General &amp;gt;&amp;gt; Features &amp;gt;&amp;gt; Notes (Beta))
   - Then attacker can enable the notes from /api/config and access other user notes&lt;/p&gt;
&lt;p&gt;### PoC
- Step 1: Log in to the application as a valid user (User A).
![image](https://github.com/user-attachments/assets/3c4625f9-6e51-4cd1-942e-6a3f467520c0)&lt;/p&gt;
&lt;p&gt;- Step 2: Intercept or inspect the response from the endpoint GET /api/config.
![image](https://github.com/user-attachments/assets/7c4fe716-314c-4640-bc9f-1e11ddc2273d)&lt;/p&gt;
&lt;p&gt;- Step 3: Observe the field &amp;#34;enable_notes&amp;#34;: false in the JSON response.
- Step 4: Manually change &amp;#34;enable_notes&amp;#34; to true using browser DevTools or by intercepting and modifying the response via a proxy like Burp Suite. (Please note, the occurrence of this API comes twice, hence modification needs to be made twice as well.)
![image](https://github.com/user-attachments/assets/99575570-a673-4508-b149-9a2480d8f62e)&lt;/p&gt;
&lt;p&gt;- Step 5: Observe the loaded frontend application; the previously hidden notes form will now be visible.
![image](https://github.com/user-attachments/assets/…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-2768</guid>
    </item>
  </channel>
</rss>
