CVE-2026-41270
Published: 23 April 2026
Summary
CVE-2026-41270 is a high-severity Improper Access Control (CWE-284) vulnerability in Flowiseai Flowise. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 13.7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as Other AI Platforms.
The strongest mitigations our analysis identified are NIST 800-53 AC-4 (Information Flow Enforcement) and CM-7 (Least Functionality).
Threat & Defense at a Glance
Threat & Defense Details
Mitigating Controls (NIST 800-53 r5)AI
SI-2 requires timely flaw remediation, directly mitigating this CVE by patching Flowise to version 3.1.0 which fixes the SSRF bypass in the NodeVM sandbox.
AC-4 enforces information flow control policies that prevent custom functions from bypassing SSRF protections to access internal network resources via unprotected Node.js modules.
CM-7 implements least functionality by restricting or disabling unnecessary network modules like Node.js http, https, and net within the sandboxed custom function environment.
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
SSRF bypass in public-facing web app (Flowise) enables T1190 for initial access; explicit support for requests to cloud metadata services enables T1552.005 for credential/data access.
NVD Description
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…
more
HTTP_DENY_LIST 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.
Deeper analysisAI
CVE-2026-41270 is a Server-Side Request Forgery (SSRF) protection bypass vulnerability in Flowise, an open-source drag-and-drop user interface for building customized large language model (LLM) flows. The issue affects versions prior to 3.1.0 and resides in the Custom Function feature, where SSRF protections are implemented via an HTTP_DENY_LIST for the axios and node-fetch libraries. However, the built-in Node.js http, https, and net modules remain unrestricted within the NodeVM sandbox, enabling attackers to circumvent these controls. The vulnerability is associated with CWE-284 (Improper Access Control) and CWE-918 (SSRF), with a CVSS v3.1 base score of 7.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L).
Authenticated users with low privileges (PR:L) can exploit this vulnerability over the network, though it requires high attack complexity (AC:H). By crafting custom functions that leverage the unprotected Node.js modules, attackers can bypass SSRF mitigations and make unauthorized requests to internal network resources, such as cloud provider metadata services. Successful exploitation grants high confidentiality and integrity impacts (C:H/I:H), along with low availability impact (A:L), potentially allowing attackers to exfiltrate sensitive data or pivot within the internal network.
The official GitHub security advisory (GHSA-xhmj-rg95-44hv) confirms that the vulnerability is fully remediated in Flowise version 3.1.0, recommending that users upgrade immediately to mitigate the risk. No additional workarounds are detailed in the provided information.
Flowise's focus on LLM orchestration introduces AI/ML relevance, as exploited instances could compromise AI workflows by accessing internal services that inform model behaviors or data pipelines. No evidence of real-world exploitation is available in the provided details.
Details
- CWE(s)
Affected Products
AI Security AnalysisAI
- AI Category
- Other AI Platforms
- Risk Domain
- N/A
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: large language model