CVE-2026-100607: Flowise through 3.1.4 Authentication Bypass via Email-Only SSO
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.
Affected Software
Event History
Frequently Asked Questions
Which deployments are exposed?
Flowise deployments through 3.1.4 are exposed when SSO is configured and an attacker can authenticate to a configured SSO provider while asserting the email address of an existing Flowise user.
Does the attacker need an existing Flowise account or the victim's password?
No. The issue is exploitable without privileges or user interaction because Flowise resolves identities by email alone rather than binding an account to a specific SSO provider and subject identifier. The attacker can use a different SSO provider or a local-password authentication method than the victim originally used.
What access could an attacker obtain?
An attacker who authenticates as an existing user can obtain complete access to that user's account, including chatflows, credentials, and API keys.