CyberRota Analysis
AI-GeneratedThe mcp-router CLI is vulnerable due to its default configuration, which exposes the MCP aggregator on all interfaces without requiring authentication unless specifically invoked with a token. This misconfiguration allows unauthorized access to the aggregator and any MCP servers it manages, posing a critical security risk. Organizations using affected versions should prioritize patching to version 0.6.3 or later to mitigate this vulnerability.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
The mcp-router CLI served its MCP aggregator on every interface and enforced authentication only when the operator asked for it. The serve command in apps/cli/src/commands/serve.ts defaulted its host to the all-interfaces address on a fixed port, and required a token only when the corresponding flag was supplied, so a default invocation exposed the aggregator, and every MCP server it fronted, to anyone able to reach the port. Release 0.6.3 defaults the host to the loopback address and refuses to start without a token whenever the host it is given is not a loopback address; no earlier release carries either check.