Which versions of Flowise are affected by CVE-2026-41273?

FlowiseAI Flowise before version 3.1.0 is vulnerable to unauthenticated OAuth token theft affecting organizations with public chatbot deployments using third-party integrations (Gmail, etc.).. A patch is available.

How to fix or mitigate CVE-2026-41273?

Within 24 hours, audit all Flowise deployments to identify which ones have public chatflows with OAuth integrations and disable or restrict public access to any chatbots connected to sensitive third-party services. Within the following week, upgrade all Flowise instances to version 3.1.0 or later and review logs for suspicious token-refresh endpoint requests that may indicate exploitation attempts. Over the following month, rotate all OAuth credentials and access tokens for any integrated services, implement network-level access controls restricting Flowise servers to internal networks only, and establish formal security review processes for OAuth integrations before future deployments.

Flowise CVE-2026-41273

Q: What is the CVSS score of CVE-2026-41273?

CVE-2026-41273 has a CVSS 4.0 base score of 7.7 (High). CVSS vector: 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.1%.

EUVD-2026-25290 HIGH

Missing Authentication for Critical Function (CWE-306)

2026-04-23 GitHub_M

GHSA-6f7g-v4pp-r667

Authentication Bypass Flowise Flowiseai

7.7

CVSS 4.0 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

7.7 HIGH

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Source Code Evidence Fetched

Jul 24, 2026 - 04:28 vuln.today

Analysis Generated

Jul 24, 2026 - 04:28 vuln.today

Patch released

Apr 24, 2026 - 19:17 nvd

Patch available

Apr 23, 2026 - 21:01 EUVD

CVSS changed

Apr 23, 2026 - 20:26 NVD

7.7 (HIGH)

EUVD ID Assigned

Apr 23, 2026 - 20:00 euvd

EUVD-2026-25290

CVE Published

Apr 23, 2026 - 19:29 nvd

HIGH 7.7

DescriptionGitHub Advisory

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.

AnalysisAI

Unauthenticated OAuth 2.0 access token disclosure in FlowiseAI Flowise before 3.1.0 lets remote attackers harvest valid third-party access tokens by chaining two unauthenticated endpoints. Because public chatflows expose their chatflowId by design, an attacker can query the public chatbot-config endpoint to read internal flowData containing OAuth credential identifiers, then invoke the unauthenticated token-refresh endpoint to mint live access tokens for services such as Gmail OAuth2. Publicly available exploit code exists (detailed PoC in the GHSA advisory); it is not listed in CISA KEV and EPSS is low (0.09%, 25th percentile).