<?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>Sat, 03 Oct 2026 16:31:47 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-11135</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-11135</link>
      <description>bdu:2026-11135</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-11135</guid>
    </item>
    <item>
      <title>EUVD-2026-344251</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344251</link>
      <description>EUVD-2026-344251</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344251</guid>
    </item>
    <item>
      <title>fkie_cve-2026-69250</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-69250</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.3, the OAuth2 token refresh endpoint POST /api/v1/oauth2-credential/refresh/:credentialId is unauthenticated by design and performs a server-side HTTP request to the credential-controlled accessTokenUrl without SSRF protections. Runtime validation confirmed that the endpoint was reachable without authentication, triggered outbound POST requests to an attacker-controlled server, reflected the full remote response body to the caller through tokenInfo, and sent client_id, client_secret, grant_type=refresh_token, and refresh_token in the request body. This issue is fixed in version 3.1.3.&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.3, the OAuth2 token refresh endpoint POST /api/v1/oauth2-credential/refresh/:credentialId is unauthenticated by design and performs a server-side HTTP request to the credential-controlled accessTokenUrl without SSRF protections. Runtime validation confirmed that the endpoint was reachable without authentication, triggered outbound POST requests to an attacker-controlled server, reflected the full remote response body to the caller through tokenInfo, and sent client_id, client_secret, grant_type=refresh_token, and refresh_token in the request body. This issue is fixed in version 3.1.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-69250</guid>
    </item>
    <item>
      <title>GHSA-r745-8hwv-h473 — Flowise: Unauthenticated OAuth2 Refresh Enables Non-Blind SSRF and Secret Exfiltration</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r745-8hwv-h473</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;The OAuth2 token refresh endpoint (`POST /api/v1/oauth2-credential/refresh/:credentialId`) is unauthenticated by design (it is in the public whitelist) and performs a server-side HTTP request to a credential-controlled URL (`accessTokenUrl`) without SSRF protections. In runtime validation, this endpoint was reachable without auth, triggered outbound POST requests to an attacker-controlled server, and reflected the full remote response body to the caller (`tokenInfo`), confirming non-blind SSRF and credential secret exfiltration.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The vulnerability is in `dist/routes/oauth2/index.js` (container runtime build), under path prefix `/api/v1/oauth2-credential`.&lt;/p&gt;
&lt;p&gt;Confirmed in runtime code:&lt;/p&gt;
&lt;p&gt;1. **Unauthenticated route via whitelist**
   - `dist/utils/constants.js` includes:
     - `/api/v1/oauth2-credential/callback`
     - `/api/v1/oauth2-credential/refresh`
   - `dist/index.js` auth middleware uses:
     - `const isWhitelisted = whitelistURLs.some((url) =&amp;gt; req.path.startsWith(url))`
   - Therefore `/api/v1/oauth2-credential/refresh/:credentialId` is treated as whitelisted.&lt;/p&gt;
&lt;p&gt;2. **User-controlled SSRF target**
   - In refresh handler (`dist/routes/oauth2/index.js`):
     - loads credential by `credentialId`
     - decrypts credential data
     - reads `accessTokenUrl`
     - executes:
       - `axios.post(tokenUrl, new URLSearchParams(refreshRequestData).toString(), ...)`
   - No `secureAxiosRequest()` / denylist wrapper is used in this path.&lt;/p&gt;
&lt;p&gt;3. **Non-blin…&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;The OAuth2 token refresh endpoint (`POST /api/v1/oauth2-credential/refresh/:credentialId`) is unauthenticated by design (it is in the public whitelist) and performs a server-side HTTP request to a credential-controlled URL (`accessTokenUrl`) without SSRF protections. In runtime validation, this endpoint was reachable without auth, triggered outbound POST requests to an attacker-controlled server, and reflected the full remote response body to the caller (`tokenInfo`), confirming non-blind SSRF and credential secret exfiltration.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The vulnerability is in `dist/routes/oauth2/index.js` (container runtime build), under path prefix `/api/v1/oauth2-credential`.&lt;/p&gt;
&lt;p&gt;Confirmed in runtime code:&lt;/p&gt;
&lt;p&gt;1. **Unauthenticated route via whitelist**
   - `dist/utils/constants.js` includes:
     - `/api/v1/oauth2-credential/callback`
     - `/api/v1/oauth2-credential/refresh`
   - `dist/index.js` auth middleware uses:
     - `const isWhitelisted = whitelistURLs.some((url) =&amp;gt; req.path.startsWith(url))`
   - Therefore `/api/v1/oauth2-credential/refresh/:credentialId` is treated as whitelisted.&lt;/p&gt;
&lt;p&gt;2. **User-controlled SSRF target**
   - In refresh handler (`dist/routes/oauth2/index.js`):
     - loads credential by `credentialId`
     - decrypts credential data
     - reads `accessTokenUrl`
     - executes:
       - `axios.post(tokenUrl, new URLSearchParams(refreshRequestData).toString(), ...)`
   - No `secureAxiosRequest()` / denylist wrapper is used in this path.&lt;/p&gt;
&lt;p&gt;3. **Non-blin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r745-8hwv-h473</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2589 — Flowise: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2589</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Flowise ausnutzen, um beliebigen Code auszuführen – sogar mit Root-Rechten –, erweiterte Privilegien zu erlangen, Sicherheitsmaßnahmen zu umgehen, Sitzungen zu kapern sowie Daten offenzulegen oder zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Flowise ausnutzen, um beliebigen Code auszuführen – sogar mit Root-Rechten –, erweiterte Privilegien zu erlangen, Sicherheitsmaßnahmen zu umgehen, Sitzungen zu kapern sowie Daten offenzulegen oder zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2589</guid>
    </item>
  </channel>
</rss>
