<?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 05:21:58 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-292835</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-292835</link>
      <description>EUVD-2026-292835</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-292835</guid>
    </item>
    <item>
      <title>fkie_cve-2026-41272</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41272</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, the core security wrappers (secureAxiosRequest and secureFetch) intended to prevent Server-Side Request Forgery (SSRF) contain multiple logic flaws. These flaws allow attackers to bypass the allow/deny lists via DNS Rebinding (Time-of-Check Time-of-Use) or by exploiting the default configuration which fails to enforce any deny list. 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, the core security wrappers (secureAxiosRequest and secureFetch) intended to prevent Server-Side Request Forgery (SSRF) contain multiple logic flaws. These flaws allow attackers to bypass the allow/deny lists via DNS Rebinding (Time-of-Check Time-of-Use) or by exploiting the default configuration which fails to enforce any deny list. This vulnerability is fixed in 3.1.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-41272</guid>
    </item>
    <item>
      <title>GHSA-2x8m-83vc-6wv4 — Flowise: SSRF Protection Bypass (TOCTOU &amp; Default Insecure)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2x8m-83vc-6wv4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise, npm: flowise-components&lt;/p&gt;
&lt;p&gt;### Summary
The core security wrappers (secureAxiosRequest and secureFetch) intended to prevent Server-Side Request Forgery (SSRF) contain multiple logic flaws. These flaws allow attackers to bypass the allow/deny lists via DNS Rebinding (Time-of-Check Time-of-Use) or by exploiting the default configuration which fails to enforce any deny list.&lt;/p&gt;
&lt;p&gt;### Details
The flaws exist in `packages/components/src/httpSecurity.ts`.&lt;/p&gt;
&lt;p&gt;Default Insecure: If process.env.HTTP_DENY_LIST is undefined, checkDenyList returns immediately, allowing all requests (including localhost).&lt;/p&gt;
&lt;p&gt;DNS Rebinding (TOCTOU): The function performs a DNS lookup (dns.lookup) to validate the IP, and then the HTTP client performs a new lookup to connect. An attacker can serve a valid IP first, then switch to an internal IP (e.g., `127.0.0.1`) for the second lookup.&lt;/p&gt;
&lt;p&gt;### PoC
Ensure `HTTP_DENY_LIST` is unset (default behavior).&lt;/p&gt;
&lt;p&gt;Use any node utilizing secureFetch to access `http://127.0.0.1`.&lt;/p&gt;
&lt;p&gt;Result: Request succeeds.&lt;/p&gt;
&lt;p&gt;#### Scenario 2: DNS Rebinding&lt;/p&gt;
&lt;p&gt;Attacker controls domain attacker.com and a custom DNS server.&lt;/p&gt;
&lt;p&gt;Configure DNS to return `1.1.1.1` (Safe IP) with TTL=0 for the first query.&lt;/p&gt;
&lt;p&gt;Configure DNS to return `127.0.0.1` (Blocked IP) for subsequent queries.&lt;/p&gt;
&lt;p&gt;Flowise validates `attacker.com` -&amp;gt; `1.1.1.1` (Allowed).&lt;/p&gt;
&lt;p&gt;Flowise fetches `attacker.com` -&amp;gt; `127.0.0.1` (Bypass).&lt;/p&gt;
&lt;p&gt;Run the following for manual verification&lt;/p&gt;
&lt;p&gt;```ts
// PoC for httpSecurity.ts Bypasses
import * as dns from &amp;#39;dns/promises&amp;#39;;&lt;/p&gt;
&lt;p&gt;// Mocking the checkDenyL…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise, npm: flowise-components&lt;/p&gt;
&lt;p&gt;### Summary
The core security wrappers (secureAxiosRequest and secureFetch) intended to prevent Server-Side Request Forgery (SSRF) contain multiple logic flaws. These flaws allow attackers to bypass the allow/deny lists via DNS Rebinding (Time-of-Check Time-of-Use) or by exploiting the default configuration which fails to enforce any deny list.&lt;/p&gt;
&lt;p&gt;### Details
The flaws exist in `packages/components/src/httpSecurity.ts`.&lt;/p&gt;
&lt;p&gt;Default Insecure: If process.env.HTTP_DENY_LIST is undefined, checkDenyList returns immediately, allowing all requests (including localhost).&lt;/p&gt;
&lt;p&gt;DNS Rebinding (TOCTOU): The function performs a DNS lookup (dns.lookup) to validate the IP, and then the HTTP client performs a new lookup to connect. An attacker can serve a valid IP first, then switch to an internal IP (e.g., `127.0.0.1`) for the second lookup.&lt;/p&gt;
&lt;p&gt;### PoC
Ensure `HTTP_DENY_LIST` is unset (default behavior).&lt;/p&gt;
&lt;p&gt;Use any node utilizing secureFetch to access `http://127.0.0.1`.&lt;/p&gt;
&lt;p&gt;Result: Request succeeds.&lt;/p&gt;
&lt;p&gt;#### Scenario 2: DNS Rebinding&lt;/p&gt;
&lt;p&gt;Attacker controls domain attacker.com and a custom DNS server.&lt;/p&gt;
&lt;p&gt;Configure DNS to return `1.1.1.1` (Safe IP) with TTL=0 for the first query.&lt;/p&gt;
&lt;p&gt;Configure DNS to return `127.0.0.1` (Blocked IP) for subsequent queries.&lt;/p&gt;
&lt;p&gt;Flowise validates `attacker.com` -&amp;gt; `1.1.1.1` (Allowed).&lt;/p&gt;
&lt;p&gt;Flowise fetches `attacker.com` -&amp;gt; `127.0.0.1` (Bypass).&lt;/p&gt;
&lt;p&gt;Run the following for manual verification&lt;/p&gt;
&lt;p&gt;```ts
// PoC for httpSecurity.ts Bypasses
import * as dns from &amp;#39;dns/promises&amp;#39;;&lt;/p&gt;
&lt;p&gt;// Mocking the checkDenyL…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2x8m-83vc-6wv4</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>
