UTC
Medium

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
What it is

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. …

What to do

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.

Affected
PackageRegistryAffectedFixed in
flowisenpm<= 3.1.33.1.4

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].