CVE-2026-41271 | FlowiseAI Flowise/flowise-components up to 3.0.x API Chain server-side request forgery (GHSA-6r77-hqx7-7vw8 / EUVD-2026-25288)

VDB-359212 · CVE-2026-41271 · GHSA-6R77-HQX7-7VW8 FLOWISEAI FLOWISE/FLOWISE-COMPONENTS UP TO 3.0.X API CHAIN SERVER-SIDE REQUEST FORGERY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.9 $0-$5k 2.19+ Summaryinfo A vulnerability classified as critical was found in FlowiseAI Flowise and flowise-components up to 3.0.x. The impacted element is an unknown function of the component API Chain Component. Executing a manipulation can lead to server-side request forgery. This vulnerability is tracked as CVE-2026-41271. The attack can be launched remotely. No exploit exists. Upgrading the affected component is advised. Detailsinfo A vulnerability has been found in FlowiseAI Flowise and flowise-components up to 3.0.x and classified as critical. This vulnerability affects an unknown function of the component API Chain Component. The manipulation with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes: 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) vulnerability exists in FlowiseAI's POST/GET API Chain components that allows unauthenticated attackers to force the server to make arbitrary HTTP requests to internal and external systems. By injecting malicious prompt templates, attackers can bypass the intended API documentation constraints and redirect requests to sensitive internal services, potentially leading to internal network reconnaissance and data exfiltration. This vulnerability is fixed in 3.1.0. The advisory is shared for download at github.com. This vulnerability was named CVE-2026-41271 since 04/18/2026. The exploitation appears to be difficult. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available. Upgrading to version 3.1.0 eliminates this vulnerability. The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-25288). Productinfo Vendor FlowiseAI Name Flowise flowise-components Version 3.0 Website Product: https://github.com/FlowiseAI/Flowise/ CPE 2.3info 🔒 🔒 CPE 2.2info 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 6.0 VulDB Meta Temp Score: 5.9 VulDB Base Score: 5.0 VulDB Temp Score: 4.8 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.1 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Server-side request forgery CWE: CWE-918 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: Flowise/flowise-components 3.1.0 Timelineinfo 04/18/2026 CVE reserved 04/23/2026 +5 days Advisory disclosed 04/23/2026 +0 days VulDB entry created 04/24/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-6r77-hqx7-7vw8 Status: Confirmed CVE: CVE-2026-41271 (🔒) GCVE (CVE): GCVE-0-2026-41271 GCVE (VulDB): GCVE-100-359212 EUVD: 🔒 Entryinfo Created: 04/23/2026 23:18 Updated: 04/24/2026 00:04 Changes: 04/23/2026 23:18 (65), 04/24/2026 00:04 (1) Complete: 🔍 Cache ID: 99:653:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸