FlowiseAI Flowise up to 3.0.x missing authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in FlowiseAI Flowise up to 3.0.x. Impacted is an unknown function. Such manipulation leads to missing authentication. This vulnerability is referenced as CVE-2026-41273. It is possible to launch the attack remotely. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, has been found in FlowiseAI Flowise up to 3.0.x. Affected by this issue is an unknown code block. The manipulation with an unknown input leads to a missing authentication vulnerability. Using CWE to declare the problem leads to CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. Impacted is 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, Flowise contains an authentication bypass vulnerability that allows an unauthenticated attacker to obtain OAuth 2.0 access tokens associated with a public chatflow. By accessing a public chatflow configuration endpoint, an attacker can retrieve internal workflow data, including OAuth credential identifiers, which can then be used to refresh and obtain valid OAuth 2.0 access tokens without authentication. This vulnerability is fixed in 3.1.0.
The advisory is available at github.com. This vulnerability is handled as CVE-2026-41273 since 04/18/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available.
Upgrading to version 3.1.0 eliminates this vulnerability.
The vulnerability is also documented in the databases at EUVD (EUVD-2026-25290) and CERT Bund (WID-SEC-2026-1145). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Affected
- Open Source Flowise
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Missing authenticationCWE: CWE-306 / CWE-287
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 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-6f7g-v4pp-r667
Status: Confirmed
CVE: CVE-2026-41273 (🔒)
GCVE (CVE): GCVE-0-2026-41273
GCVE (VulDB): GCVE-100-359210
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 (67), 04/24/2026 00:04 (1), 04/25/2026 06:45 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.