Servers and applications
GHSA-vcwp-f9rq-3887
Flowise Custom MCP npx package execution leads to authenticated server-side command execution
- Severity
- Critical 9.0
- Published
- 31 Aug 2026
- Last changed
- 31 Aug 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.1.4
- Attack
- Over the network · Only under certain conditions · Needs a user account · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H- Sources
- Project advisories (GitHub)
Description
Flowise is an open-source visual platform for building LLM applications, chatflows, agents, and tool integrations. Flowise includes a Custom MCP node that lets users configure Model Context Protocol servers. In Flowise 3.1.2, the Custom MCP stdio configuration allows the command npx and only blocks a limited set of dangerous flags. Because npx can install and run arbitrary npm package binaries, an authenticated attacker can execute code on the Flowise server without using shell metacharacters, node -e, or python -c.
The issue was validated against the official Docker image running Flowise 3.1.2. A safe proof of concept used npx shx touch through the Custom MCP node load method. Flowise returned a normal "No Available Actions" response because shx is not an MCP server, but the marker file was created inside the container before MCP initialization failed.
Affected software
| Software | Affected versions |
|---|---|
FlowiseServers and applications · github:flowiseai/flowise |
|
About Flowise
Build AI Agents, Visually
- Archived
- Yes, no longer maintainedGitHub
- Weekly downloads (npm)
- 6,604npm, 15 Nov 2026
- Docker Hub pulls
- 7,390,661Docker Hub, 15 Nov 2026
- GitHub stars
- 55,573GitHub, 15 Nov 2026
- Forks
- 25,094GitHub, 15 Nov 2026
- Latest release
- [email protected]GitHub, 15 Nov 2026
- Released
- 29 Jul 2026GitHub
- First published on GitHub
- 31 Mar 2023GitHub
Source code Website Docker image Package
Vulnerabilities in Flowise
- In our list
- 171
- Published in the last 12 months
- 149
- Critical, last 12 months
- 41
- High, last 12 months
- 70
- Known exploited
- 0
- CVE-2026-130796Flowise 3.1.3 through 3.1.4 MCP Server Token Disclosure via Public Chatflow EndpointHigh 8.8 17 Nov 2026
- CVE-2026-130615Flowise through 3.1.4 SSRF via DNS Rebinding in Playwright and Puppeteer LoadersHigh 7.6 17 Nov 2026
- CVE-2026-127214Flowise 3.1.4 SSRF Bypass via Custom Function SandboxMedium 6.3 13 Nov 2026
- CVE-2026-119978Flowise through 3.1.4 Custom Function Sandbox Escape RCE via LocalFileStoreCritical 9.0 30 Oct 2026
- CVE-2026-90580A vulnerability was found in FlowiseAI Flowise up to 3.0.2. This vulnerability affects the function axios.post of the file packages/server/src/controllers/evaluations/index.ts of the component Evaluations Endpoint. The manipulation of the argument Host/X-Forwarded-Proto results in server-side request forgery. The attack may be launched remotely. The exploit has been made public and could be…Low 2.1 13 Sept 2026
- CVE-2026-90535Flowise versions before 3.1.4 contain an unauthenticated denial of service vulnerability in the /api/v1/text-to-speech/abort endpoint that accepts user-supplied chatflowId and chatId without ownership verification. Attackers can terminate active chatflow predictions for any user by submitting requests with known chatflow and chat identifiers, causing targeted service disruption.Medium 6.3 12 Sept 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-vcwp-f9rq-3887
- github.com https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-vcwp-f9rq-3887