FlowiseAI Flowise/flowise-components up to 3.0.x API Chain server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
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.
Details
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 databases at EUVD (EUVD-2026-25288) and CERT Bund (WID-SEC-2026-1145). Once again VulDB remains the best source for vulnerability data.
Affected
- Open Source Flowise
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB 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): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 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: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Flowise/flowise-components 3.1.0
Timeline
04/18/2026 CVE reserved04/23/2026 Advisory disclosed
04/23/2026 VulDB entry created
04/25/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-6r77-hqx7-7vw8
Status: Confirmed
CVE: CVE-2026-41271 (🔒)
GCVE (CVE): GCVE-0-2026-41271
GCVE (VulDB): GCVE-100-359212
EUVD: 🔒
CERT Bund: WID-SEC-2026-1145 - Flowise: Mehrere Schwachstellen
Entry
Created: 04/23/2026 23:18Updated: 04/25/2026 06:45
Changes: 04/23/2026 23:18 (65), 04/24/2026 00:04 (1), 04/25/2026 06:45 (7)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.