<?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, 18 Oct 2026 10:28:08 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-275502</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-275502</link>
      <description>EUVD-2026-275502</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-275502</guid>
    </item>
    <item>
      <title>fkie_cve-2026-31829</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-31829</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.0.13, Flowise exposes an HTTP Node in AgentFlow and Chatflow that performs server-side HTTP requests using user-controlled URLs. By default, there are no restrictions on target hosts, including private/internal IP ranges (RFC 1918), localhost, or cloud metadata endpoints. This enables Server-Side Request Forgery (SSRF), allowing any user interacting with a publicly exposed chatflow to force the Flowise server to make requests to internal network resources that are inaccessible from the public internet. This vulnerability is fixed in 3.0.13.&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.0.13, Flowise exposes an HTTP Node in AgentFlow and Chatflow that performs server-side HTTP requests using user-controlled URLs. By default, there are no restrictions on target hosts, including private/internal IP ranges (RFC 1918), localhost, or cloud metadata endpoints. This enables Server-Side Request Forgery (SSRF), allowing any user interacting with a publicly exposed chatflow to force the Flowise server to make requests to internal network resources that are inaccessible from the public internet. This vulnerability is fixed in 3.0.13.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-31829</guid>
    </item>
    <item>
      <title>GHSA-fvcw-9w9r-pxc7 — Flowise affected by Server-Side Request Forgery (SSRF) in HTTP Node Leading to Internal Network Access</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fvcw-9w9r-pxc7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise, npm: flowise-components&lt;/p&gt;
&lt;p&gt;**Description:**
Flowise exposes an HTTP Node in AgentFlow and Chatflow that performs server-side HTTP requests using user-controlled URLs. By default, there are no restrictions on target hosts, including private/internal IP ranges (RFC 1918), localhost, or cloud metadata endpoints.
This enables Server-Side Request Forgery (SSRF), allowing any user interacting with a publicly exposed chatflow to force the Flowise server to make requests to internal network resources that are inaccessible from the public internet.&lt;/p&gt;
&lt;p&gt;**Impact includes:**
- Access to internal admin panels (e.g., internal company dashboards, Jenkins, Kubernetes API, etc.).
- Retrieval of cloud provider metadata (e.g., AWS IMDSv1 at [http://169.254.169.254], GCP, Azure).
- Port scanning and enumeration of internal services.
- Potential lateral movement or privilege escalation in compromised environments.&lt;/p&gt;
&lt;p&gt;This vulnerability is particularly severe because:
- Flowise instances are often deployed publicly without authentication (FLOWISE_USERNAME/PASSWORD not set by default).
- The HTTP Node is easily accessible in simple flows with minimal configuration.&lt;/p&gt;
&lt;p&gt;**Proof of Concept (PoC):**
A minimal flow consisting of three nodes demonstrates successful internal network access:
Flow Structure:
&amp;lt;img width=&amp;#34;1131&amp;#34; height=&amp;#34;323&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/f6ddc74f-3ae9-4376-995a-693fb272627a&amp;#34; /&amp;gt;
HTTP Node Configuration:
The HTTP Node is configured to perform a GET request to an internal address o…&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;**Description:**
Flowise exposes an HTTP Node in AgentFlow and Chatflow that performs server-side HTTP requests using user-controlled URLs. By default, there are no restrictions on target hosts, including private/internal IP ranges (RFC 1918), localhost, or cloud metadata endpoints.
This enables Server-Side Request Forgery (SSRF), allowing any user interacting with a publicly exposed chatflow to force the Flowise server to make requests to internal network resources that are inaccessible from the public internet.&lt;/p&gt;
&lt;p&gt;**Impact includes:**
- Access to internal admin panels (e.g., internal company dashboards, Jenkins, Kubernetes API, etc.).
- Retrieval of cloud provider metadata (e.g., AWS IMDSv1 at [http://169.254.169.254], GCP, Azure).
- Port scanning and enumeration of internal services.
- Potential lateral movement or privilege escalation in compromised environments.&lt;/p&gt;
&lt;p&gt;This vulnerability is particularly severe because:
- Flowise instances are often deployed publicly without authentication (FLOWISE_USERNAME/PASSWORD not set by default).
- The HTTP Node is easily accessible in simple flows with minimal configuration.&lt;/p&gt;
&lt;p&gt;**Proof of Concept (PoC):**
A minimal flow consisting of three nodes demonstrates successful internal network access:
Flow Structure:
&amp;lt;img width=&amp;#34;1131&amp;#34; height=&amp;#34;323&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/f6ddc74f-3ae9-4376-995a-693fb272627a&amp;#34; /&amp;gt;
HTTP Node Configuration:
The HTTP Node is configured to perform a GET request to an internal address o…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fvcw-9w9r-pxc7</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0689 — Flowise: Schwachstelle ermöglicht Manipulation von Dateien</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0689</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Flowise ausnutzen, um serverseitige Request-Forgery-Angriffe durchzuführen, Daten zu manipulieren und vertrauliche Informationen offenzulegen, was möglicherweise eine laterale Bewegung oder eine Ausweitung von Berechtigungen ermöglichen kann.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Flowise ausnutzen, um serverseitige Request-Forgery-Angriffe durchzuführen, Daten zu manipulieren und vertrauliche Informationen offenzulegen, was möglicherweise eine laterale Bewegung oder eine Ausweitung von Berechtigungen ermöglichen kann.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0689</guid>
    </item>
  </channel>
</rss>
