<?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>Fri, 16 Oct 2026 10:31:05 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-5941</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-5941</link>
      <description>EUVD-2026-5941</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-5941</guid>
    </item>
    <item>
      <title>fkie_cve-2024-37895</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-37895</link>
      <description>&lt;p&gt;Lobe Chat is an open-source LLMs/AI chat framework. In affected versions if an attacker can successfully authenticate through SSO/Access Code, they can obtain the real backend API Key by modifying the base URL to their own attack URL on the frontend and setting up a server-side request. This issue has been addressed in version 0.162.25. Users are advised to upgrade. There are no known workarounds for this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Lobe Chat is an open-source LLMs/AI chat framework. In affected versions if an attacker can successfully authenticate through SSO/Access Code, they can obtain the real backend API Key by modifying the base URL to their own attack URL on the frontend and setting up a server-side request. This issue has been addressed in version 0.162.25. Users are advised to upgrade. There are no known workarounds for this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-37895</guid>
    </item>
    <item>
      <title>GHSA-p36r-qxgx-jq2v — Lobe Chat API Key Leak</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p36r-qxgx-jq2v</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @lobehub/chat&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;If an attacker can successfully authenticate through SSO/Access Code, they can obtain the real backend API Key by modifying the base URL to their own attack URL on the frontend and setting up a server-side request.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The attack process is described above.&lt;/p&gt;
&lt;p&gt;![image](https://github.com/lobehub/lobe-chat/assets/36695271/df5e0c3c-af28-45c3-959f-182cc9d06680)&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;Frontend:
1. Pass basic authentication (SSO/Access Code).
2. Set the Base URL to a private attack address.
3. Configure the request method to be a server-side request.
4. At the self-set attack address, retrieve the API Key information from the request headers.&lt;/p&gt;
&lt;p&gt;Backend:
1. The LobeChat version allows setting the Base URL.
2. There is no outbound traffic whitelist.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;All community version LobeChat users using SSO/Access Code authentication, tested on version 0.162.13.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @lobehub/chat&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;If an attacker can successfully authenticate through SSO/Access Code, they can obtain the real backend API Key by modifying the base URL to their own attack URL on the frontend and setting up a server-side request.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The attack process is described above.&lt;/p&gt;
&lt;p&gt;![image](https://github.com/lobehub/lobe-chat/assets/36695271/df5e0c3c-af28-45c3-959f-182cc9d06680)&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;Frontend:
1. Pass basic authentication (SSO/Access Code).
2. Set the Base URL to a private attack address.
3. Configure the request method to be a server-side request.
4. At the self-set attack address, retrieve the API Key information from the request headers.&lt;/p&gt;
&lt;p&gt;Backend:
1. The LobeChat version allows setting the Base URL.
2. There is no outbound traffic whitelist.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;All community version LobeChat users using SSO/Access Code authentication, tested on version 0.162.13.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p36r-qxgx-jq2v</guid>
    </item>
  </channel>
</rss>
