Flowise before 3.1.3 validates Custom MCP stdio environment variables against a denylist using a case-sensitive comparison, so on Windows, where environment names are case-insensitive, supplying 'node_options' bypasses the NODE_OPTIONS denylist entry. An authenticated user who can configure a Custom MCP node can thereby inject NODE_OPTIONS --require and execute arbitrary code in the Flowise server context.
Fix
Public exploits 2
- Flowise 3.1.3 - arbitrary code execution (webapps · multiple) Exploit-DB · 2026-07-07
- CerberusMrXi/Flowise-CVE-2026-58057-exploit PoC on GitHub
Each line links to the index that lists it, never to exploit code. Exploit-DB's "verified" and a Metasploit rank of good or better count as verified; a PoC-in-GitHub entry is a repository's claim.
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/FlowiseAI/Flowise/pull/6471 Issue Tracking, Patch
- https://www.vulncheck.com/advisories/flowise-custom-mcp-environment-variable-denylist-bypass-via-case-sensitivity Exploit, Patch, Third Party Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 2.3 · flowiseaiNVD modified 2026-10-25 17:10
Affected (CPE criteria) 1
cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*
References 3
- https://github.com/FlowiseAI/Flowise/pull/6471 Issue Tracking, Patch
- https://github.com/bikini/exploitarium/tree/main/flowise-mcp-env-case-bypass-poc Exploit, Third Party Advisory
- https://www.vulncheck.com/advisories/flowise-custom-mcp-environment-variable-denylist-bypass-via-case-sensitivity Exploit, Patch, Third Party Advisory