CVE-2026-41271

Flowise: APIChain Prompt Injection SSRF in GET/POST API Chains

This SSRF vulnerability allows unauthenticated attackers to abuse the FlowiseAI server as a proxy to make HTTP requests to arbitrary internal and external endpoints, leading to:

• Internal Network Reconnaissance: Ability to scan and map internal network services, ports, and applications that are not exposed to the internet
• Cloud Metadata Access: Potential access to cloud provider metadata services that may contain temporary credentials and sensitive configuration data
• Internal Service Exploitation: Interaction with internal APIs, databases, and services that trust requests originating from the Flowise server
• Data Exfiltration: Access to sensitive internal data through compromised internal services
• Bypassing Security Controls: Circumvention of firewall rules and network segmentation by using the Flowise server as a pivot point

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2026-41271 has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.1.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-41271? CVE-2026-41271 is a high-severity server-side request forgery (SSRF) vulnerability in flowise (npm), affecting versions <= 3.0.13. It is fixed in 3.1.0. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. How severe is CVE-2026-41271? CVE-2026-41271 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-41271?
   • flowise (npm) (versions <= 3.0.13)
   • flowise-components (npm) (versions <= 3.0.13)
4. Is there a fix for CVE-2026-41271? Yes. CVE-2026-41271 is fixed in 3.1.0. Upgrade to this version or later.
5. Is CVE-2026-41271 exploitable, and should I be worried? Whether CVE-2026-41271 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-41271 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-41271?
   • Upgrade flowise to 3.1.0 or later
   • Upgrade flowise-components to 3.1.0 or later