<?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-14T16:14:05.324293+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/bdu:2026-07196</id>
    <title>bdu:2026-07196</title>
    <updated>2026-10-14T16:14:05.411255+00:00</updated>
    <content>bdu:2026-07196</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-07196"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-319373</id>
    <title>EUVD-2026-319373</title>
    <updated>2026-10-14T16:14:05.411290+00:00</updated>
    <content>EUVD-2026-319373</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-319373"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-45339</id>
    <title>fkie_cve-2026-45339</title>
    <updated>2026-10-14T16:14:05.411304+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 0.9.0, Open WebUI allows admins to restrict which API endpoints an API key can access. When an API key is restricted from /api/v1/messages, requests using the Authorization: Bearer sk-... header are correctly blocked with 403. However, the same key sent via the x-api-key header bypasses the restriction entirely — the request is authenticated, the model is invoked, and a full response is returned. This vulnerability is fixed in 0.9.0.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-45339"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-57q6-fvp4-pqmm</id>
    <title>GHSA-57q6-fvp4-pqmm — Open WebUI's API key endpoint restrictions bypassed via `x-api-key` header — full message processing on restricted endp…</title>
    <updated>2026-10-14T16:14:05.411338+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: open-webu</p>
<p>### Summary</p>
<p>Open WebUI allows admins to restrict which API endpoints an API key can access. When an API key is restricted from `/api/v1/messages`, requests using the `Authorization: Bearer sk-...` header are correctly blocked with 403. However, the same key sent via the `x-api-key` header bypasses the restriction entirely — the request is authenticated, the model is invoked, and a full response is returned.</p>
<p>### Details</p>
<p>Open WebUI's Anthropic-compatible API path accepts authentication via `x-api-key` header (standard for the Anthropic API). The endpoint restriction check only applies to keys presented via the `Authorization` header. When the same `sk-...` key is supplied in `x-api-key`, the restriction check is skipped but the key is still valid for authentication.</p>
<p>This means any API key, regardless of its configured endpoint restrictions, can access any API endpoint by simply using `x-api-key` instead of `Authorization`.</p>
<p>### PoC</p>
<p>**Verified against Open WebUI v0.8.11.**</p>
<p>**Setup:** Admin creates a user with an API key that has endpoint restrictions (not allowed on `/api/v1/messages`). A mock OpenAI-compatible model (`mock-model`) is configured.</p>
<p>```bash
API_KEY="sk-dc56016d720e49ba9e95584d602b79bb"</p>
<p># Test 1: Authorization header — BLOCKED (endpoint restriction enforced)
curl -s -X POST http://target:8080/api/v1/messages \
  -H "Authorization: Bearer $API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"model":"mock-model","messages":[{"role":"user","content":"via…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-57q6-fvp4-pqmm"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-3543</id>
    <title>PYSEC-2026-3543 — Open WebUI's API key endpoint restrictions bypassed via `x-api-key` header — full message processing on restricted endp…</title>
    <updated>2026-10-14T16:14:05.411393+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>Open WebUI allows admins to restrict which API endpoints an API key can access. When an API key is restricted from `/api/v1/messages`, requests using the `Authorization: Bearer sk-...` header are correctly blocked with 403. However, the same key sent via the `x-api-key` header bypasses the restriction entirely — the request is authenticated, the model is invoked, and a full response is returned.</p>
<p>### Details</p>
<p>Open WebUI's Anthropic-compatible API path accepts authentication via `x-api-key` header (standard for the Anthropic API). The endpoint restriction check only applies to keys presented via the `Authorization` header. When the same `sk-...` key is supplied in `x-api-key`, the restriction check is skipped but the key is still valid for authentication.</p>
<p>This means any API key, regardless of its configured endpoint restrictions, can access any API endpoint by simply using `x-api-key` instead of `Authorization`.</p>
<p>### PoC</p>
<p>**Verified against Open WebUI v0.8.11.**</p>
<p>**Setup:** Admin creates a user with an API key that has endpoint restrictions (not allowed on `/api/v1/messages`). A mock OpenAI-compatible model (`mock-model`) is configured.</p>
<p>```bash
API_KEY="sk-dc56016d720e49ba9e95584d602b79bb"</p>
<p># Test 1: Authorization header — BLOCKED (endpoint restriction enforced)
curl -s -X POST http://target:8080/api/v1/messages \
  -H "Authorization: Bearer $API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"model":"mock-model","messages":[{"role":"user","content":"via…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-3543"/>
  </entry>
</feed>
