UTC
High

Flowise: Cross-workspace credential IDOR in openai-assistants-vector-store

CVE-2026-70472 · GHSA-chm3-vqcf-52rx · published 2026-08-04

Severity
High
CVSS score
7.1
Chance of exploitation (EPSS)
0.52%
Fixed in
3.1.3
  • Exploitation Public proof of concept
  • Automatable No
  • Technical impact Partial
  • CISA SSVC
What it is

Cross-workspace unauthorized use of stored OpenAI keys. Unauthorized read/modify/delete of victim vector stores and files. Direct billing impact on victim OpenAI account. Multi-tenant boundary violation with practical exploitability.

What to do

Upgrade flowise to 3.1.3 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.

Affected
PackageRegistryAffectedFixed in
flowisenpm<= 3.1.23.1.3

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). 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].