CVE-2026-100607

Flowise through 3.1.4 Authentication Bypass via Email-Only SSO

Published Sep 26, 2026 CVSS 4.0 · 9.2 Critical EPSS < 1% KEV · Not listed
Description
Flowise through 3.1.4 resolves SSO and local-password users solely by email without storing provider or subject identifier bindings, allowing attackers to authenticate as any existing user by claiming their email at any configured SSO provider. Attackers can gain complete account access including chatflows, credentials, and API keys by authenticating through a different SSO provider or local password than the victim's original registration method.

Analysis

AI-generated

Technical impact

Flowise through 3.1.4 allows attackers to authenticate as any existing user by assuming the user’s email address, because the system does not store bindings between the email and the SSO provider or subject identifier. As a result, an attacker who can claim any email can gain complete access to an account, including chatflows, credentials, and API keys. The vulnerability is a classic authentication bypass identified as CWE‑287 and has the potential to compromise confidentiality, integrity and availability of user data.

Affected Systems

The flaw impacts FlowiseAI Flowise deployments running version 3.1.4 or earlier. All users who rely on email-only SSO or who registered with a local password are vulnerable if they are using a configuration that does not enforce provider or subject identifiers. No other versions or products are known to be affected.

Risk and Exploitability

With a CVSS score of 9.2, the vulnerability is considered critical. The EPSS score is not available, and the flaw is not listed in CISA KEV, but the lack of provider binding allows an attacker to bypass authentication remotely with only the victim’s email address. Attackers can exploit the flaw by accessing any configured SSO provider or by creating a local password login for the target email. The attack can be performed from any network location that can reach the Flowise instance, making it a high‑risk exposure for exposed services.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Flowise to version 3.1.5 or later where the issue is fixed.
  • Disable or restrict email‑only SSO until an update is applied, ensuring that SSO providers must be explicitly bound to user identifiers.
  • Reconfigure SSO settings to enforce provider and subject identifier bindings for each user to prevent impersonation.

Generated by OpenCVE AI on September 26, 2026 at 14:55 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Flowise through 3.1.4 resolves SSO and local-password users solely by email without storing provider or subject identifier bindings, allowing attackers to authenticate as any existing user by claiming their email at any configured SSO provider. Attackers can gain complete account access including chatflows, credentials, and API keys by authenticating through a different SSO provider or local password than the victim's original registration method.
Title Flowise through 3.1.4 Authentication Bypass via Email-Only SSO
First Time appeared Flowiseai
Flowiseai flowise
Weaknesses CWE-287
CPEs cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*
Vendors & Products Flowiseai
Flowiseai flowise
References
Metrics cvssV3_1

{'score': 7.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L'}

cvssV4_0

{'score': 9.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 28, 2026, 5:07 PM
Reserved
Sep 26, 2026, 2:30 AM
Status
Deferred
Published
Sep 26, 2026, 2:16 PM
Modified
Sep 28, 2026, 6:17 PM