Flowise RCE via Custom MCP Config Node
CVE-2026-73601 · GHSA-g98q-rm45-q9h8 · published 2026-07-29 · updated 2026-08-20
- Severity
- Critical
- CVSS score
- 9.0
- Chance of exploitation (EPSS)
- Not scored
- Fixed in
- 3.1.3
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
An authenticated user on a Flowise instance that did not have the CUSTOM_MCP_PROTOCOL=sse environment variable set could exploit this RCE vulnerability, resulting in full compromise of the application.
Upgrade flowise to 3.1.3 or later, and flowise-components 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.
The default setting for the CUSTOM_MCP_PROTOCOL Flowise environment variable should be sse, due to the risk of RCE the StdioClientTransport client introduces. A deny-list approach for validating environment variables is not recommended, as there are likely other methods to achieve RCE via environment variables that are not documented in this report.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| flowise | npm | <= 3.1.2 | 3.1.3 |
| flowise-components | npm | <= 3.1.2 | 3.1.3 |
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- CriticalFlowise Prompt Injection to RCE and SSRF via CSV/Airtable Agent Python Validator Bypassflowise, flowise-components
- CriticalCross-IdP account takeover via email-only SSO matchingflowise
- CriticalINVITED users auto-promoted via SSO email match (invite-token bypass)flowise
- CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
The impact, patch and workaround text comes from the advisory, shortened (published by Flowise). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.