CVE-2026-41270: Flowise: SSRF Protection Bypass via Unprotected Built-in HTTP Modules in Custom Function Sandbox
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, a Server-Side Request Forgery (SSRF) protection bypass vulnerability exists in the Custom Function feature. While the application implements SSRF protection via HTTPDENYLIST for axios and node-fetch libraries, the built-in Node.js http, https, and net modules are allowed in the NodeVM sandbox without equivalent protection. This allows authenticated users to bypass SSRF controls and access internal network resources (e.g., cloud provider metadata services) This vulnerability is fixed in 3.1.0.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41270?
CVE-2026-41270 is considered a high-severity vulnerability due to the potential for server-side request forgery (SSRF).
How do I fix CVE-2026-41270?
To fix CVE-2026-41270, upgrade your Flowise installation to version 3.1.0 or later.
What impact does CVE-2026-41270 have on my application?
CVE-2026-41270 allows attackers to bypass SSRF protections, potentially leading to unauthorized access to internal services.
Which versions of Flowise are affected by CVE-2026-41270?
Flowise versions prior to 3.1.0 are affected by CVE-2026-41270.
Is exploitation of CVE-2026-41270 easy to achieve?
Yes, exploitation of CVE-2026-41270 can be relatively straightforward for an attacker familiar with the affected configurations.