FlowiseAI Flowise/flowise-components up to 3.0.x secureAxiosRequest/secureFetch server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in FlowiseAI Flowise and flowise-components up to 3.0.x. This affects an unknown function of the component secureAxiosRequest/secureFetch. The manipulation leads to server-side request forgery. This vulnerability is listed as CVE-2026-41272. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability was found in FlowiseAI Flowise and flowise-components up to 3.0.x and classified as critical. This issue affects an unknown functionality of the component secureAxiosRequest/secureFetch. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, the core security wrappers (secureAxiosRequest and secureFetch) intended to prevent Server-Side Request Forgery (SSRF) contain multiple logic flaws. These flaws allow attackers to bypass the allow/deny lists via DNS Rebinding (Time-of-Check Time-of-Use) or by exploiting the default configuration which fails to enforce any deny list. This vulnerability is fixed in 3.1.0.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-41272 since 04/18/2026. The exploitation is known to be difficult. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 3.1.0 eliminates this vulnerability.
The vulnerability is also documented in the databases at EUVD (EUVD-2026-25289) and CERT Bund (WID-SEC-2026-1145). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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-2x8m-83vc-6wv4
Status: Confirmed
CVE: CVE-2026-41272 (🔒)
GCVE (CVE): GCVE-0-2026-41272
GCVE (VulDB): GCVE-100-359213
EUVD: 🔒
CERT Bund: WID-SEC-2026-1145 - Flowise: Mehrere Schwachstellen
Entry
Created: 04/23/2026 23:19Updated: 04/25/2026 06:45
Changes: 04/23/2026 23:19 (65), 04/24/2026 00:04 (1), 04/25/2026 06:45 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.