Description
Flowise through 3.1.4 (Enterprise/platform mode with SSO enabled) contains an authentication bypass in the SSO login path. When an SSO callback arrives with an email matching a user whose status is INVITED, verifyAndLogin (SSOBase.ts:80-94) copies the user record from the database — including the server-stored single-use invitation tempToken — into the data passed to AccountService.register(). The register handler's token lookup, email match, and expiry checks therefore pass trivially against the server's own token instead of a caller-supplied one, and the account and its organization membership are flipped to ACTIVE. As a result, anyone able to authenticate at any configured SSO provider using a pending invitee's email address as the email claim can take over that invitation and obtain the invited user's access to the organization without ever possessing the emailed invitation token, for as long as the invitation is valid (24 hours by default). At the time of the advisory no patched version was available.
Published: 2026-09-26
Score: 9.2 Critical
EPSS: < 1% Very Low
KEV: No
Impact: Authentication bypass allowing an attacker to gain an invited user’s organization access
Action: Assess Impact
AI Analysis

Impact

A flaw in Flowise’s SSO login path allows an authentication bypass, which is a classic instance of CWE‑287: Improper Authentication. The bypass occurs when the callback from an SSO provider contains an email that matches a pending invitee; the system mistakenly copies the invitation‑token from the server’s database into the registration flow and validates it as if it were supplied by the attacker. As a result, the attacker can activate the invite and become an active member of the organization without knowing the original invitation code or privileged credentials. The impact is the ability to assume the role and permissions of the invited user, potentially exposing sensitive data or allowing further lateral movement.

Affected Systems

Flowise AI’s Flowise product, version 3.1.4, is affected when the application runs in enterprise or platform mode with SSO authentication enabled. Any tenant using this configuration and issuing new invitations is susceptible until a patch is applied.

Risk and Exploitability

The vulnerability has a CVSS v3.1 score of 9.2, indicating very high severity. No EPSS score is available and the flaw is not listed in the CISA Known Exploit Vulnerabilities catalog. The likely attack vector is remote via an SSO provider: an attacker needs only the ability to trigger an SSO callback with the target’s pending invitee email and the invitation must still be within the default 24‑hour validity window. Once triggered, the attacker can take over the invitation and gain active organization membership with no additional credentials.

Generated by OpenCVE AI on September 26, 2026 at 15:25 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor’s patched version of Flowise as soon as it becomes available.
  • Revoke all pending invitations and disable invitation‑based SSO access until a fix is released.
  • Implement or enforce stricter SSO validation rules that require the invitation token to be supplied by the caller or that validate incoming SSO tokens against a protected store rather than trusting the email claim alone.

Generated by OpenCVE AI on September 26, 2026 at 15:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 28 Sep 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

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


Sat, 26 Sep 2026 13:30:00 +0000

Type Values Removed Values Added
Description Flowise through 3.1.4 (Enterprise/platform mode with SSO enabled) contains an authentication bypass in the SSO login path. When an SSO callback arrives with an email matching a user whose status is INVITED, verifyAndLogin (SSOBase.ts:80-94) copies the user record from the database — including the server-stored single-use invitation tempToken — into the data passed to AccountService.register(). The register handler's token lookup, email match, and expiry checks therefore pass trivially against the server's own token instead of a caller-supplied one, and the account and its organization membership are flipped to ACTIVE. As a result, anyone able to authenticate at any configured SSO provider using a pending invitee's email address as the email claim can take over that invitation and obtain the invited user's access to the organization without ever possessing the emailed invitation token, for as long as the invitation is valid (24 hours by default). At the time of the advisory no patched version was available.
Title Flowise through 3.1.4 Authentication Bypass via SSO Email Match
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'}


Subscriptions

Flowiseai Flowise
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-09-28T19:10:36.679Z

Reserved: 2026-09-26T02:30:34.352Z

Link: CVE-2026-100606

cve-icon Vulnrichment

Updated: 2026-09-28T19:09:04.613Z

cve-icon NVD

Status : Deferred

Published: 2026-09-26T14:16:40.820

Modified: 2026-09-28T19:16:43.523

Link: CVE-2026-100606

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-26T17:30:14Z

Weaknesses