<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T16:43:46.600617+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-280242</id>
    <title>EUVD-2026-280242</title>
    <updated>2026-10-08T16:43:46.603420+00:00</updated>
    <content>EUVD-2026-280242</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-280242"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-34222</id>
    <title>fkie_cve-2026-34222</title>
    <updated>2026-10-08T16:43:46.603452+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to version 0.8.11, there is a broken access control vulnerability in tool values. This issue has been patched in version 0.8.11.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-34222"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-7429-hxcv-268m</id>
    <title>GHSA-7429-hxcv-268m — Open WebUI has Broken Access Control in Tool Valves</title>
    <updated>2026-10-08T16:43:46.603482+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: open-webui</p>
<p># Summary</p>
<p>## Broken Access Control in Tool Valves</p>
<p>Open WebUI supports function calling through "Tools". Function calling allows an LLM to reliably connect to external tools and interact with external APIs. Exemplary use-cases include connecting to an internal knowledge base, retrieving emails from an exchange server, or retrieving order data from a shop backend.</p>
<p>These interactions often require the LLM to authenticate against backend services using API keys specifically created for a technical (Open WebUI) user.</p>
<p>To simplify configuration and secret handling, Open WebUI implements "Valves" and "UserValves" that allow users and administrators to input dynamic details like API keys or configuration options.</p>
<p>Valves have the following distinction:</p>
<p>- **Valves:** Configurable by admins only.
- **UserValves:** Configurable by any user.</p>
<p>The Tool Valves endpoint does not properly restrict read access to the valve. This allows a low privileged user to access all data contained within the valve. In the worst case, this gives a low privileged "Member" user access to sensitive Tool data, such as API keys for third-party systems.</p>
<p>---</p>
<p># Details</p>
<p>## 1) Broken Access Control in Tool Valves</p>
<p>The following steps can be performed to reproduce the vulnerability.</p>
<p>**1.** An administrator creates an Open WebUI Tool with a configured Valve.</p>
<p>&lt;img width="1038" height="597" alt="image" src="https://github.com/user-attachments/assets/f79bdde9-18fa-49e4-a6c3-5077731f0815" /&gt;</p>
<p>**2.** The adminis…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-7429-hxcv-268m"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-2709</id>
    <title>PYSEC-2026-2709 — Open WebUI has Broken Access Control in Tool Valves</title>
    <updated>2026-10-08T16:43:46.603545+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: open-webui</p>
<p># Summary</p>
<p>## Broken Access Control in Tool Valves</p>
<p>Open WebUI supports function calling through "Tools". Function calling allows an LLM to reliably connect to external tools and interact with external APIs. Exemplary use-cases include connecting to an internal knowledge base, retrieving emails from an exchange server, or retrieving order data from a shop backend.</p>
<p>These interactions often require the LLM to authenticate against backend services using API keys specifically created for a technical (Open WebUI) user.</p>
<p>To simplify configuration and secret handling, Open WebUI implements "Valves" and "UserValves" that allow users and administrators to input dynamic details like API keys or configuration options.</p>
<p>Valves have the following distinction:</p>
<p>- **Valves:** Configurable by admins only.
- **UserValves:** Configurable by any user.</p>
<p>The Tool Valves endpoint does not properly restrict read access to the valve. This allows a low privileged user to access all data contained within the valve. In the worst case, this gives a low privileged "Member" user access to sensitive Tool data, such as API keys for third-party systems.</p>
<p>---</p>
<p># Details</p>
<p>## 1) Broken Access Control in Tool Valves</p>
<p>The following steps can be performed to reproduce the vulnerability.</p>
<p>**1.** An administrator creates an Open WebUI Tool with a configured Valve.</p>
<p>&lt;img width="1038" height="597" alt="image" src="https://github.com/user-attachments/assets/f79bdde9-18fa-49e4-a6c3-5077731f0815" /&gt;</p>
<p>**2.** The adminis…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-2709"/>
  </entry>
</feed>
