Summary
CVE-2026-100607 is a critical authentication bypass vulnerability in Flowise, an open-source generative AI/LLM application builder, affecting all versions through 3.1.4. The flaw resides in Flowise’s single sign-on (SSO) implementation, which resolves users solely by email address across identity providers and local password authentication without validating a stable, provider-specific identity binding. An unauthenticated attacker can exploit this to fully take over any existing user account, including administrator accounts, by authenticating as that user’s email through a different SSO provider or via local password registration.
Technical details
- Root cause: Flowise’s
SSOBase.verifyAndLogin()logic looks up users exclusively viauserService.readUserByEmail(email)and never compares the identity provider’s stable subject identifier (profile.id/sub) against a stored binding for that account. - Trigger conditions: The target deployment must have SSO enabled with more than one identity provider configured, or SSO enabled alongside local password authentication. The attack is easiest against identity providers that do not enforce strict email verification (e.g., an Auth0 tenant configured with
verify_email_on_signup: false). - Attack vector: Network — the attacker registers or authenticates through an alternate, attacker-controllable identity provider (or local password signup) using the victim’s known or guessed email address; Flowise treats this as the same account with no additional proof of ownership.
- Impact: Full account takeover, including read access to chatflows, stored credentials, chat/message history, and API keys belonging to the victim; if the victim is an administrator, this extends to organization-wide settings modification and data tampering.
Affected software
- Flowise (FlowiseAI), all versions 0 through 3.1.4 (
pkg:npm/flowise) - Primarily impacts deployments (including Enterprise deployments) with multiple SSO providers configured, or SSO combined with local password authentication
Severity
- CVSS v3.1 Base Score: 7.7 (High) —
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L - CVSS v4.0 Base Score: 9.2 (Critical) —
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
Mitigation and recommended actions
- Immediate: No patched version has been published at the time of disclosure. Monitor FlowiseAI’s official releases and advisory for a fixed version and upgrade as soon as one is available.
- Workarounds/network mitigations (until patched):
- Disable local password authentication for any deployment where SSO is enabled.
- Restrict SSO configuration to a single, trusted identity provider rather than multiple providers.
- Ensure the configured identity provider enforces strict, verified email ownership (e.g., avoid
verify_email_on_signup: falsestyle settings). - Audit user accounts and authentication logs for suspicious cross-provider or dual-authentication login patterns.
- Restrict network exposure of the Flowise login/SSO endpoints to trusted networks where possible.

