<?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>Sun, 04 Oct 2026 11:21:40 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-292985</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-292985</link>
      <description>EUVD-2026-292985</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-292985</guid>
    </item>
    <item>
      <title>fkie_cve-2026-41266</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41266</link>
      <description>&lt;p&gt;Flowise is a drag &amp;amp; drop user interface to build a customized large language model flow. Prior to 3.1.0, /api/v1/public-chatbotConfig/:id ep exposes sensitive data including API keys, HTTP authorization headers and internal configuration without any authentication. An attacker with knowledge just of a chatflow UUID can retrieve credentials stored in password type fields and HTTP headers, leading to credential theft and more. This vulnerability is fixed in 3.1.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Flowise is a drag &amp;amp; drop user interface to build a customized large language model flow. Prior to 3.1.0, /api/v1/public-chatbotConfig/:id ep exposes sensitive data including API keys, HTTP authorization headers and internal configuration without any authentication. An attacker with knowledge just of a chatflow UUID can retrieve credentials stored in password type fields and HTTP headers, leading to credential theft and more. This vulnerability is fixed in 3.1.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-41266</guid>
    </item>
    <item>
      <title>GHSA-4jpm-cgx2-8h37 — Flowise: Sensitive Data Leak in public-chatbotConfig</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4jpm-cgx2-8h37</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`/api/v1/public-chatbotConfig/:id `ep exposes sensitive data including API keys, HTTP authorization headers and internal configuration without any authentication. An attacker with knowledge just of a chatflow UUID can retrieve credentials stored in password type fields and HTTP headers, leading to credential theft and more.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Knowledge of chatflow UUID can be obtained from embedded chat widgets, referrer headers or logs and it&amp;#39;s the only prerequest.&lt;/p&gt;
&lt;p&gt;`getSinglePublicChatbotConfig` function in `packages/server/src/services/chatflows/index.ts` returns the full **flowData** object without authorization check or data sanitization.&lt;/p&gt;
&lt;p&gt;There is a comment as **&amp;#34;Safe as public endpoint as chatbotConfig doesn&amp;#39;t contain sensitive credential&amp;#34;** but **flowData** does contain sensitive data such as:&lt;/p&gt;
&lt;p&gt;`type: &amp;#39;password&amp;#39;` fields are stored in plaintext (unstructuredAPIKey in S3File node).
HTTP Authorization headers in POST / GET Requests nodes.
Internal API endpoints and webhook URLs.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;- Add an S3 File node, set &amp;#34;File Processing Method&amp;#34; to &amp;#34;Unstructured&amp;#34;.
- Enter an API key in &amp;#34;Unstructured API KEY&amp;#34; field or add a Requests Post node with Authorization header.
- Save the chatflow.&lt;/p&gt;
&lt;p&gt;`curl -s &amp;#34;https://localhost/api/v1/public-chatbotConfig/{CHATFLOW_UUID}&amp;#34;`&lt;/p&gt;
&lt;p&gt;Response:&lt;/p&gt;
&lt;p&gt;```
{
  &amp;#34;flowData&amp;#34;: &amp;#34;{...\&amp;#34;unstructuredAPIKey\&amp;#34;:\&amp;#34;victim_key\&amp;#34;...\&amp;#34;requestsPostHeaders\&amp;#34;:\&amp;#34;Bearer victim_token\&amp;#34;...}&amp;#34;
}
```&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Impacts all Flowise Cloud users with chatflows containing p…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`/api/v1/public-chatbotConfig/:id `ep exposes sensitive data including API keys, HTTP authorization headers and internal configuration without any authentication. An attacker with knowledge just of a chatflow UUID can retrieve credentials stored in password type fields and HTTP headers, leading to credential theft and more.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Knowledge of chatflow UUID can be obtained from embedded chat widgets, referrer headers or logs and it&amp;#39;s the only prerequest.&lt;/p&gt;
&lt;p&gt;`getSinglePublicChatbotConfig` function in `packages/server/src/services/chatflows/index.ts` returns the full **flowData** object without authorization check or data sanitization.&lt;/p&gt;
&lt;p&gt;There is a comment as **&amp;#34;Safe as public endpoint as chatbotConfig doesn&amp;#39;t contain sensitive credential&amp;#34;** but **flowData** does contain sensitive data such as:&lt;/p&gt;
&lt;p&gt;`type: &amp;#39;password&amp;#39;` fields are stored in plaintext (unstructuredAPIKey in S3File node).
HTTP Authorization headers in POST / GET Requests nodes.
Internal API endpoints and webhook URLs.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;- Add an S3 File node, set &amp;#34;File Processing Method&amp;#34; to &amp;#34;Unstructured&amp;#34;.
- Enter an API key in &amp;#34;Unstructured API KEY&amp;#34; field or add a Requests Post node with Authorization header.
- Save the chatflow.&lt;/p&gt;
&lt;p&gt;`curl -s &amp;#34;https://localhost/api/v1/public-chatbotConfig/{CHATFLOW_UUID}&amp;#34;`&lt;/p&gt;
&lt;p&gt;Response:&lt;/p&gt;
&lt;p&gt;```
{
  &amp;#34;flowData&amp;#34;: &amp;#34;{...\&amp;#34;unstructuredAPIKey\&amp;#34;:\&amp;#34;victim_key\&amp;#34;...\&amp;#34;requestsPostHeaders\&amp;#34;:\&amp;#34;Bearer victim_token\&amp;#34;...}&amp;#34;
}
```&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Impacts all Flowise Cloud users with chatflows containing p…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4jpm-cgx2-8h37</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1145 — Flowise: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1145</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Flowise ausnutzen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, um Informationen offenzulegen, und um Dateien zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Flowise ausnutzen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, um Informationen offenzulegen, und um Dateien zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1145</guid>
    </item>
  </channel>
</rss>
