CVE-2026-91930 FlowiseAI CVE debrief

Who should care

Flowise administrators, security teams, and organizations using Flowise with multi-tenant setups should assess exposure and implement compensating controls. These stakeholders should prioritize remediation efforts due to the high severity of the vulnerability. Security teams should review the official advisory and CVE record to validate affected scope, severity, and vendor guidance. Additionally, they should monitor organization and workspace membership

Why it matters

CVE-2026-91930 is a high-severity vulnerability in Flowise that allows authenticated users to gain administrative access to victim organizations. Flowise administrators and security teams should assess exposure, implement compensating controls, and prioritize remediation efforts.

• Authenticated users can add themselves as organization owners
• Attackers can create workspaces and gain administrative access to victim organizations
• Insufficient tenant isolation allows for potential lateral movement
• Verification of affected versions and remediation steps is required

Technical summary

Flowise before 3.1.4 fails to scope enterprise organization and workspace membership APIs to the caller's tenant, allowing authenticated users to supply arbitrary organization IDs and potentially gain administrative access to victim organizations. This vulnerability is caused by insufficient tenant isolation in the organizationuser and workspace endpoints. Attackers can exploit this vulnerability to add themselves as organization owners, create workspaces, and gain administrative access to victim organizations. Flowise administrators and security teams should assess exposure and implement compensating controls.

Defensive priority

High priority for organizations using Flowise, especially those with multi-tenant setups

Recommended defensive actions

• Review and update Flowise to version 3.1.4 or later
• Assess exposure and implement compensating controls for multi-tenant setups
• Monitor organization and workspace membership APIs for suspicious activity
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but specific affected versions and remediation steps require verification from official sources. The vulnerability is caused by insufficient tenant isolation in the organizationuser and workspace endpoints, allowing authenticated users to supply arbitrary organization IDs. Evidence of exploitation includes suspicious activity in organization and workspace membership APIs. Defenders should verify the affected versions, review the official advisory, and implement compens

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.