Executive brief
Flowise is a low-code platform for building LLM applications that integrates with cloud services like Google Drive, Google Sheets, and AWS. A vulnerability in versions up to 3.1.3 allows a low-privilege user in one workspace to access and use credentials belonging to another workspace, enabling them to enumerate victim resources (such as files, spreadsheets, and database tables) by acting on behalf of the victim through the platform. While the attacker cannot directly steal the credential secrets, they can leverage the platform to perform unauthorized actions against third-party services using the victim's credentials.
Technical details
This is a broken access control / IDOR (Insecure Direct Object Reference) vulnerability combined with a confused deputy issue. The POST /api/v1/node-load-method/:name endpoint lacks route-level permission checks and fails to validate that the credential ID supplied by the attacker belongs to the caller's workspace before invoking loadMethods. The vulnerable code path resolves credentials by raw Credential.id via getCredentialData() without enforcing workspace-scoping, unlike other credential APIs which check Credential.workspaceId. An authenticated low-privilege user or workspace API key can supply a credential UUID owned by another workspace and cause the platform to decrypt and use that credential server-side, returning provider metadata (e.g., DynamoDB table names, Google Drive file listings). Attack requires network access and valid authentication to Flowise, but no special privileges beyond basic user access. The fix is implemented in version 3.1.4.
Affected products
- FlowiseAI Flowise up to and including 3.1.3
Timeline
- 2026-08-28: disclosed: GitHub Security Advisory GHSA-hqvm-7539-v83j published
- 2026-09-12: advisory: CVE-2026-90534 published on NVD
- 2026-09-12: patched: Fix released in version 3.1.4