Bugfix/Custom MCP Security #4963
Conversation
HenryHengZJ
commented
Jul 28, 2025
HenryHengZJ
commented
- Implemented a validation function to check for banned commands and dangerous patterns.
- Added checks for potential shell injection attempts in command and arguments.
- Security validation is conditionally enabled based on environment variable CUSTOM_MCP_SECURITY_CHECK.
…dangerous patterns. - Added checks for potential shell injection attempts in command and arguments. - Security validation is conditionally enabled based on environment variable CUSTOM_MCP_SECURITY_CHECK.
…upergatewayMCP. Added checks for banned commands, dangerous patterns, and potential shell injection attempts. Security validation is conditionally enabled based on the CUSTOM_MCP_SECURITY_CHECK environment variable.
|
Does it solve https://nvd.nist.gov/vuln/detail/CVE-2025-8943? |
|
Hi team, After analyzing the stable version (main branch), I noticed that the security function introduced through the PR to mitigate the vulnerability, Instead, a new function called When testing the latest version against the available exploits (using Docker Compose to deploy a local instance), it appears that the application remains vulnerable to the same CVE. 
Are you planning to release a new patch for this vulnerability, or is this the intended behavior? For context, I enabled the 
Edit: I think I found the PR that removed the security checks: https://github.com/FlowiseAI/Flowise/pull/5003/commits |
|
This PR #5232 will enable security check by default, and here's the recommended settings when deployed on cloud in production: # Enable security validation (default)
CUSTOM_MCP_SECURITY_CHECK=true
# Use SSE protocol for better security
CUSTOM_MCP_PROTOCOL=sse |
