<?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>Mon, 05 Oct 2026 23:38:07 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-09509</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-09509</link>
      <description>bdu:2026-09509</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-09509</guid>
    </item>
    <item>
      <title>EUVD-2026-319291</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-319291</link>
      <description>EUVD-2026-319291</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-319291</guid>
    </item>
    <item>
      <title>fkie_cve-2026-44567</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-44567</link>
      <description>&lt;p&gt;Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.1.124, the API does not properly validate that the user has an authorized user role of user. By default, when Open WebUI is configured with new sign-ups enabled, the default user role is set to pending. In this configuration, an administrator is required to go into the Admin management panel following a new user registration and reconfigure the user to have a role of either user or admin before that user is able to access the web application. This vulnerability is fixed in 0.1.124.&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.1.124, the API does not properly validate that the user has an authorized user role of user. By default, when Open WebUI is configured with new sign-ups enabled, the default user role is set to pending. In this configuration, an administrator is required to go into the Admin management panel following a new user registration and reconfigure the user to have a role of either user or admin before that user is able to access the web application. This vulnerability is fixed in 0.1.124.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-44567</guid>
    </item>
    <item>
      <title>GHSA-4vg5-rp28-gvjf — Open WebUI has Improper Authorization Control</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4vg5-rp28-gvjf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: open-webui&lt;/p&gt;
&lt;p&gt;# **CONFIDENTIAL**&lt;/p&gt;
&lt;p&gt;# Vulnerability Disclosure Analysis Documentation&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Vulnerability Details&lt;/p&gt;
&lt;p&gt;| # | Field | Value |
|---|-------|-------|
| 1 | **Discoverer** | Taylor Pennington of KoreLogic, Inc. |
| 2 | **Date Submitted** | June 11, 2024 |
| 3 | **Title** | Open WebUI Improper Authorization Control |
| 5 | **Affected Vendor** | Open WebUI |
| 6 | **Affected Product(s)** | Open WebUI (Formerly Ollama WebUI) |
| 7 | **Affected Version(s)** | 0.1.105 |
| 8 | **Platform/OS** | Debian GNU/Linux 12 (bookworm) |
| 9 | **Vector** | HTTP web interface |
| 10 | **CWE** | 285 Improper Authorization |&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## 4. High-level Summary&lt;/p&gt;
&lt;p&gt;There is a missing authorization check affecting user accounts with a `pending` status allowing the user to make authenticated API calls as a `user` context.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## 11. Technical Analysis&lt;/p&gt;
&lt;p&gt;The Open WebUI web application has three user role classifications: `user`, `admin`, and `pending`. By default, when Open WebUI is configured with `new sign-ups` enabled, the default user role is set to `pending`. In this configuration, an administrator is required to go into the Admin management panel following a new user registration and reconfigure the user to have a role of either `user` or `admin` before that user is able to access the web application. However, this check is only enforced at the client presentation layer, the API does not properly validate that the user has an authorized user role of `user`.&lt;/p&gt;
&lt;p&gt;### Request&lt;/p&gt;
&lt;p&gt;```http
POST /api/v1/auths/signup…&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;# **CONFIDENTIAL**&lt;/p&gt;
&lt;p&gt;# Vulnerability Disclosure Analysis Documentation&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Vulnerability Details&lt;/p&gt;
&lt;p&gt;| # | Field | Value |
|---|-------|-------|
| 1 | **Discoverer** | Taylor Pennington of KoreLogic, Inc. |
| 2 | **Date Submitted** | June 11, 2024 |
| 3 | **Title** | Open WebUI Improper Authorization Control |
| 5 | **Affected Vendor** | Open WebUI |
| 6 | **Affected Product(s)** | Open WebUI (Formerly Ollama WebUI) |
| 7 | **Affected Version(s)** | 0.1.105 |
| 8 | **Platform/OS** | Debian GNU/Linux 12 (bookworm) |
| 9 | **Vector** | HTTP web interface |
| 10 | **CWE** | 285 Improper Authorization |&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## 4. High-level Summary&lt;/p&gt;
&lt;p&gt;There is a missing authorization check affecting user accounts with a `pending` status allowing the user to make authenticated API calls as a `user` context.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## 11. Technical Analysis&lt;/p&gt;
&lt;p&gt;The Open WebUI web application has three user role classifications: `user`, `admin`, and `pending`. By default, when Open WebUI is configured with `new sign-ups` enabled, the default user role is set to `pending`. In this configuration, an administrator is required to go into the Admin management panel following a new user registration and reconfigure the user to have a role of either `user` or `admin` before that user is able to access the web application. However, this check is only enforced at the client presentation layer, the API does not properly validate that the user has an authorized user role of `user`.&lt;/p&gt;
&lt;p&gt;### Request&lt;/p&gt;
&lt;p&gt;```http
POST /api/v1/auths/signup…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4vg5-rp28-gvjf</guid>
    </item>
    <item>
      <title>PYSEC-2026-2703 — Open WebUI has Improper Authorization Control</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-2703</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: open-webui&lt;/p&gt;
&lt;p&gt;# **CONFIDENTIAL**&lt;/p&gt;
&lt;p&gt;# Vulnerability Disclosure Analysis Documentation&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Vulnerability Details&lt;/p&gt;
&lt;p&gt;| # | Field | Value |
|---|-------|-------|
| 1 | **Discoverer** | Taylor Pennington of KoreLogic, Inc. |
| 2 | **Date Submitted** | June 11, 2024 |
| 3 | **Title** | Open WebUI Improper Authorization Control |
| 5 | **Affected Vendor** | Open WebUI |
| 6 | **Affected Product(s)** | Open WebUI (Formerly Ollama WebUI) |
| 7 | **Affected Version(s)** | 0.1.105 |
| 8 | **Platform/OS** | Debian GNU/Linux 12 (bookworm) |
| 9 | **Vector** | HTTP web interface |
| 10 | **CWE** | 285 Improper Authorization |&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## 4. High-level Summary&lt;/p&gt;
&lt;p&gt;There is a missing authorization check affecting user accounts with a `pending` status allowing the user to make authenticated API calls as a `user` context.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## 11. Technical Analysis&lt;/p&gt;
&lt;p&gt;The Open WebUI web application has three user role classifications: `user`, `admin`, and `pending`. By default, when Open WebUI is configured with `new sign-ups` enabled, the default user role is set to `pending`. In this configuration, an administrator is required to go into the Admin management panel following a new user registration and reconfigure the user to have a role of either `user` or `admin` before that user is able to access the web application. However, this check is only enforced at the client presentation layer, the API does not properly validate that the user has an authorized user role of `user`.&lt;/p&gt;
&lt;p&gt;### Request&lt;/p&gt;
&lt;p&gt;```http
POST /api/v1/auths/signup…&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;# **CONFIDENTIAL**&lt;/p&gt;
&lt;p&gt;# Vulnerability Disclosure Analysis Documentation&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Vulnerability Details&lt;/p&gt;
&lt;p&gt;| # | Field | Value |
|---|-------|-------|
| 1 | **Discoverer** | Taylor Pennington of KoreLogic, Inc. |
| 2 | **Date Submitted** | June 11, 2024 |
| 3 | **Title** | Open WebUI Improper Authorization Control |
| 5 | **Affected Vendor** | Open WebUI |
| 6 | **Affected Product(s)** | Open WebUI (Formerly Ollama WebUI) |
| 7 | **Affected Version(s)** | 0.1.105 |
| 8 | **Platform/OS** | Debian GNU/Linux 12 (bookworm) |
| 9 | **Vector** | HTTP web interface |
| 10 | **CWE** | 285 Improper Authorization |&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## 4. High-level Summary&lt;/p&gt;
&lt;p&gt;There is a missing authorization check affecting user accounts with a `pending` status allowing the user to make authenticated API calls as a `user` context.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## 11. Technical Analysis&lt;/p&gt;
&lt;p&gt;The Open WebUI web application has three user role classifications: `user`, `admin`, and `pending`. By default, when Open WebUI is configured with `new sign-ups` enabled, the default user role is set to `pending`. In this configuration, an administrator is required to go into the Admin management panel following a new user registration and reconfigure the user to have a role of either `user` or `admin` before that user is able to access the web application. However, this check is only enforced at the client presentation layer, the API does not properly validate that the user has an authorized user role of `user`.&lt;/p&gt;
&lt;p&gt;### Request&lt;/p&gt;
&lt;p&gt;```http
POST /api/v1/auths/signup…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-2703</guid>
    </item>
  </channel>
</rss>
