CVE-2026-81094
The mcp-router CLI served its MCP aggregator on every interface and …
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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/mcp-router/mcp-router
- github.com/mcp-router/mcp-router/blob/v0.6.3/apps/cli/src/commands/serve.ts#L105
- github.com/mcp-router/mcp-router/commit/4c4642cfd274097ec8b33ecd3047390829c79d35
- github.com/mcp-router/mcp-router/security/advisories/GHSA-rx55-5c7h-r56r
- www.vulncheck.com/advisories/mcp-router-cli-before-0.6.3-binds-the-mcp-aggregator-to-all-i
- nvd.nist.gov/vuln/detail/CVE-2026-81094
- cve.org/CVERecord?id=CVE-2026-81094
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.