Cross-workspace credential IDOR in node-load-method allows low-privilege users to enumerate victim third-party resources
GHSA-hqvm-7539-v83j · published 2026-08-28
- Severity
- Medium
- CVSS score
- 6.1
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 3.1.4
A low-privilege authenticated user can use Flowise as a confused deputy against third-party accounts configured in another workspace. The attacker can: enumerate victim Google Drive file IDs, file names, MIME categories, and modified timestamps; enumerate victim Google Sheets spreadsheet IDs and names; enumerate victim AWS DynamoDB table names and compatible key schema metadata; trigger OAuth refresh or AWS STS AssumeRole flows through credentials outside the attacker's workspace; consume provider API quota; create provider-side audit events under the victim credential. This crosses both a Flowise workspace boundary and an external provider account boundary. …
Upgrade flowise to 3.1.4 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Add an explicit permission gate to POST /api/v1/node-load-method/:name. Before invoking any load method, collect credential IDs from nodeData.credential and nested config fields and verify they belong to req.user.activeWorkspaceId or are explicitly shared with that workspace. Replace generic getCredentialData(id) in server-invoked load methods with a workspace-aware resolver. Make workspace context mandatory for credential resolution. Add regression tests: Workspace A can call node-load-method with a Workspace A credential. Workspace A cannot call node-load-method with a Workspace B credential. Workspace A can call node-load-method only if Workspace B explicitly shared that credential.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| flowise | npm | <= 3.1.3 | 3.1.4 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- CriticalFlowise Prompt Injection to RCE and SSRF via CSV/Airtable Agent Python Validator Bypassflowise, flowise-components
- CriticalCross-IdP account takeover via email-only SSO matchingflowise
- CriticalINVITED users auto-promoted via SSO email match (invite-token bypass)flowise
- CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
The impact, patch and workaround text comes from the advisory, shortened (published by Flowise). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.