A critical authorization flaw in MCPHub allows authenticated users to perform unauthorized actions across tenant boundaries, posing a severe risk to data confidentiality.

The vulnerability exists in the tool execution API, which fails to enforce ownership checks that are correctly applied elsewhere in the application. Any authenticated user can interact with MCP servers they do not own, effectively bypassing intended tenant isolation.

Successful exploitation allows an attacker to perform cross-tenant compromise, including arbitrary host file reads and Server-Side Request Forgery (SSRF). Given the CVSS score of 7.7, this vulnerability represents a high risk, as it enables unauthorized access to sensitive cloud API keys, secrets, and internal filesystem data, potentially leading to a full breach of the affected infrastructure.

Immediate Action: Upgrade to MCPHub version 1.0.30 or later, which includes the necessary authorization logic to enforce server ownership during tool execution.

Proactive Monitoring: Review application access logs for unusual patterns of tool execution, specifically focusing on API calls originating from non-admin accounts that reference server IDs not associated with their user profile.

Compensating Controls: Implement strict network segmentation and egress filtering to mitigate the impact of potential SSRF attacks while the update is being staged for deployment.

Public Exploit Available: No (exploit_available: false)

This vulnerability presents a significant security risk by enabling unauthorized access to sensitive data and infrastructure through cross-tenant exploitation. Organizations utilizing MCPHub must prioritize the transition to version 1.0.30 immediately to close this authorization gap and prevent potential data exfiltration or internal network compromise.