FLOWISE · GHSA-mgrx-3hqw-485h · Package
NO FIX YET
Flowise through 3.1.4 with SSO enabled can auto-activate a user whose invitation is still pending when an SSO login arrives with that user's email address. An attacker who can authenticate at any configured SSO provider with the invitee's email gets the invited user's organization access without the emailed invitation token.
first public Sep 26, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running Flowise 3.1.4 or earlier in Enterprise/platform mode with SSO enabled. Deployments without SSO, or on a fixed release, are not affected by this path. This advisory is a withdrawn duplicate of GHSA-vf3j-89vf-r697, so check that entry for the authoritative details.
Not affected if single-user-mode, sso-disabled
Who cares cwe-287, flowise, npm, self-hosted, sso
npm ls flowise or the image tag) against the range in the advisory.No fix yet, per the sources.
This advisory has been withdrawn because it is a duplicate of GHSA-vf3j-89vf-r697. This link is maintained to preserve external references.
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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.