Flowise
Flowise - Remote Code Execution via MCP Security Bypass in validateCommandFlags and validateArgsForLocalFileAccess
Flowise before 3.1.2 contains multiple OS command injection vulnerabilities in the Custom MCP Server feature due to incomplete command-flag validation and a regex bypass in local file access restrictions. An attacker with a Flowise account of any role, or API access with view/update permissions for chatflows, can configure a malicious MCP server to bypass the validateCommandFlags blocklist (for example, 'docker build' is not blocked, and 'npx --yes' is not blocked while only '-y' is) and the validateArgsForLocalFileAccess checks, resulting in execution of arbitrary commands on the Flowise host.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.1.2
Fixed in 3.1.2
- < 3.1.2
Fixed in 3.1.2
Mitigation
Upgrade Flowise to 3.1.2 or later.
Upgrade Flowise Components to 3.1.2 or later.
References
- Vendor advisory github.com/FlowiseAI/Flowise/security/advisori…
Timeline
Days relative to CVE publicationFirst public PoC 5.4 days after publication; not in CISA KEV. First PoC: Metasploit exploit: Flowise MCP Server Remote Code Execution (exploit/multi/http/flowise_mcp_rce) (Metasploit, 28 Jun 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| Metasploit | Metasploit exploit: Flowise MCP Server Remote Code Execution (exploit/multi/http/flowise_mcp_rce) | 28 Jun 2026 | 14 Nov 2026 |