Flowise Custom MCP npx package execution leads to authenticated server-side command execution
GHSA-vcwp-f9rq-3887 · published 2026-08-31
- Severity
- Critical
- CVSS score
- 9.0
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 3.1.4
A successful attacker can execute commands as the Flowise process inside the container. Practical impact includes: Reading Flowise configuration, local files, and environment variables accessible to the process. Accessing credentials stored on disk or exposed through the runtime environment. Modifying Flowise data and application files accessible to the process. Running network tools from the container to pivot to internal services reachable from the Flowise deployment. Denial of service by consuming resources, deleting accessible files, or terminating processes. …
Upgrade flowise to 3.1.4 or later, and flowise-components to 3.1.4 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.
Recommended fixes: 1. Remove npx from the Custom MCP stdio command allowlist. 2. Do not permit runtime package installation or package execution from user-supplied MCP configuration. 3. If stdio MCP is required, allow only administrator-installed MCP server binaries by absolute path. 4. Add a strict package or binary allowlist maintained by administrators, not users. 5. Require route-level authorization for /api/v1/node-load-method/customMCP and all Custom MCP configuration paths. 6. Disable Custom MCP stdio execution for untrusted users. 7. Run MCP subprocesses in a sandbox with no secrets, a read-only filesystem, restricted network access, and resource limits. …
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| flowise | npm | <= 3.1.3 | 3.1.4 |
| flowise-components | npm | <= 3.1.3 | 3.1.4 |
- 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.