Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.2%top 56%

CVE-2026-41273: CWE-306: Missing Authentication for Critical Function in FlowiseAI Flowise

0
High
VulnerabilityCVE-2026-41273cvecve-2026-41273cwe-306
Published: Thu Apr 23 2026 (04/23/2026, 19:29:16 UTC)
Source: CVE Database V5
Vendor/Project: FlowiseAI
Product: Flowise

Description

Flowise versions prior to 3. 1. 0 have an authentication bypass vulnerability that allows unauthenticated attackers to obtain OAuth 2. 0 access tokens linked to public chatflows. By accessing a public chatflow configuration endpoint, attackers can retrieve internal workflow data including OAuth credential identifiers, enabling them to refresh and acquire valid OAuth tokens without authentication. This vulnerability is fixed in version 3. 1. 0.

CVSS v4.0

Score 7.7high

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vuln. Confidentiality
None
Vuln. Integrity
Low
Vuln. Availability
None
Subsq. Confidentiality
High
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:H/SI:N/SA:N

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 05/01/2026, 20:44:25 UTC

Technical Analysis

CVE-2026-41273 is a high-severity authentication bypass vulnerability (CWE-306) in FlowiseAI's Flowise product versions before 3.1.0. The flaw allows unauthenticated attackers to access a public chatflow configuration endpoint and retrieve sensitive internal workflow data, including OAuth credential identifiers. These credentials can be used to refresh and obtain valid OAuth 2.0 access tokens without any authentication, potentially compromising OAuth-protected resources. The vulnerability is resolved in Flowise version 3.1.0.

Potential Impact

An attacker exploiting this vulnerability can obtain valid OAuth 2.0 access tokens without authentication, potentially leading to unauthorized access to resources protected by these tokens. This could result in unauthorized actions or data exposure within systems relying on these OAuth credentials.

Mitigation Recommendations

Upgrade Flowise to version 3.1.0 or later, where this authentication bypass vulnerability is fixed. Since no official patch links or vendor advisory are provided, verify the upgrade from the official FlowiseAI sources before deployment. Patch status is not yet confirmed by vendor advisory; check official vendor communications for current remediation guidance.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-04-18T14:01:46.801Z
Cvss Version
4.0
State
PUBLISHED
Remediation Level
null

Threat ID: 69ea782987115cfb6850f83a

Added to database: 4/23/2026, 7:51:05 PM

Last enriched: 5/1/2026, 8:44:25 PM

Last updated: 6/7/2026, 7:23:39 PM

Views: 95

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses