Executive brief
Flowise is a platform for building AI workflows and assistants. Versions before 3.1.4 contain authorization gaps in Enterprise-tier features that allow authenticated users to perform unauthorized actions across tenant boundaries—including deleting other organizations' workspaces, modifying roles, inviting themselves to other organizations, and accessing stored SSO secrets belonging to other tenants. This can lead to data destruction, unauthorized access to customer information, and operational disruption across multiple customers in a multi-tenant deployment.
Technical details
The vulnerability is a series of missing authorization checks (CWE-862) across five Enterprise endpoints that fail to verify resource ownership before performing operations. Affected endpoints include DELETE /api/v1/workspace/{id} (allows cross-tenant workspace deletion), POST /api/v1/account/invite (self-invitation to arbitrary workspaces), PUT/DELETE /api/v1/organizationuser (cross-org role modification), PUT /api/v1/role (modification of foreign org roles via id-only fetch), and POST /api/v1/loginmethod/test (reuse of encrypted SSO secrets from other orgs). All require Enterprise license activation or Enterprise platform mode; an attacker must be an authenticated user with Enterprise access on the target instance. The root cause is absence of organization/workspace ownership assertions before mutation, despite such checks existing elsewhere in the codebase. Patches are available in version 3.1.4.
Affected products
- Flowise Flowise before 3.1.4
Timeline
- 2026-08-31: disclosed: GHSA-7x8x-vv46-4579 published on GitHub
- 2026-09-15: patched: Version 3.1.4 released with fix
- 2026-09-15: advisory: CVE-2026-91929 published