Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-100607 – Authentication Bypass / Account Takeover – Flowise ≤ 3.1.4

Be the first to know when new zero-days emerge:

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 via userService.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: false style 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.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge