UTC
Medium

Flowise: Path Traversal in Vector Store basePath

GHSA-w6v6-49gh-mc9w · published 2026-04-16

Severity
Medium
CVSS score
4.9
Chance of exploitation (EPSS)
No CVE
Fixed in
3.1.0
What it is

An authenticated attacker can: 1. Write files to arbitrary locations on the server filesystem 2. Overwrite existing files if the process has write permissions 3. Potential for code execution by writing to web-accessible directories or startup scripts 4. Data exfiltration by writing to network-mounted filesystems

What to do

Upgrade flowise to 3.1.0 or later, and flowise-components to 3.1.0 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.0.133.1.0
flowise-componentsnpm<= 3.0.133.1.0

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