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

Back
New CVE Detected

CVE-2026-100606 – SSO Authentication Bypass / Invitation Takeover – Flowise Enterprise ≤ 3.1.4

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-100606 is a critical authentication bypass in FlowiseAI’s Flowise Enterprise SSO login flow. When a Single Sign-On callback presents an email address matching a user in "INVITED" status, Flowise’s SSOBase.verifyAndLogin logic retrieves the server-stored invitation tempToken from its own database and replays it back into the account-registration validation routine, allowing the invitation to be silently completed without ever possessing the real invite link. The issue carries a CVSS score of 9.2 (Critical) and affects Flowise Enterprise deployments through version 3.1.4.

Technical details

  • Root cause: SSOBase.verifyAndLogin (in SSOBase.ts) spreads the full database user record — including its tempToken — into the authentication payload it hands to accountService.register(). Because register() validates the token against the same database row the SSO path just read it from, the check always succeeds, regardless of whether the caller ever saw the token.
  • Trigger conditions: A Flowise Enterprise organization has an active, unexpired invitation (default 24-hour window) for a target email address, and SSO is configured for the organization.
  • Attack vector: Network. An attacker only needs the ability to authenticate to the organization’s configured SSO/identity provider using the invitee’s email address as the identity claim (e.g., an unverified or attacker-controlled email at the IdP) — no interaction from the victim and no prior credentials for Flowise itself are required.
  • Impact: The attacker’s SSO session is auto-promoted to the invited user’s account with Member-level access, gaining entry to the organization’s chatflows, stored credentials, workspace/user listings, and audit logs. The legitimate invitee’s original invitation link is invalidated in the process (its token is cleared), which can serve as a detection signal.

Affected software

  • Flowise (npm package flowise), Enterprise/platform mode with SSO and user invitations enabled — versions 0 through 3.1.4.

Severity

  • CVSS v4.0 Base Score: 9.2 (Critical)
  • 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

Mitigation and recommended actions

  • Immediate: No patched version has been released; the FlowiseAI/Flowise GitHub repository was archived (read-only) on August 13, 2026, so no vendor fix is expected. Organizations relying on Flowise Enterprise SSO invitations should treat this as unpatchable and plan migration away from the affected invitation/SSO flow.
  • Workarounds/network mitigations (no patch available):
    • Disable or suspend pending user invitations while SSO is enabled, or disable SSO login until invitations are processed through the email-link flow only.
    • Reduce the invitation expiry window (INVITE_TOKEN_EXPIRY_IN_HOURS) from the 24-hour default to 1–2 hours to shrink the exploitation window.
    • Require and enforce the identity provider’s email_verified claim before accepting SSO logins for invited accounts.
    • Monitor for invitees reporting an "INVALID_TEMP_TOKEN" error on their invitation link, which indicates the token was already consumed by another session.
    • Audit-log and alert on invitation acceptances separately from normal SSO logins, and review organization membership/audit logs for unexpected Member-level accounts.
    • Restrict network exposure of Flowise Enterprise admin/SSO endpoints to trusted networks where feasible.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge