CyberRota Analysis
AI-GeneratedMCPHub versions prior to 1.0.32 are vulnerable to a Server-Side Request Forgery (SSRF) due to inadequate filtering of certain IPv6 address families, allowing attackers to access internal infrastructure by encoding private IPv4 addresses. This vulnerability poses a high risk, as it can lead to unauthorized access to sensitive resources within the network. Organizations using MCPHub should prioritize upgrading to version 1.0.32 to mitigate this security risk.
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
MCPHub is a unified hub for centrally managing and dynamically orchestrating multiple MCP servers/APIs into separate endpoints with flexible routing strategies. Prior to version 1.0.32, MCPHub's SSRF guard in src/utils/ssrf.ts uses a custom isBlockedIpv6 function that only checks for loopback, link-local, unique-local, IPv4-mapped, and IPv4-compatible IPv6 addresses. IPv6 transition address families -- NAT64 (64:ff9b::/96), 6to4 (2002::/16), and Teredo (2001::/32) -- are not checked. An attacker who can specify a URL for an MCP server connection can encode a private IPv4 address inside one of these IPv6 forms to bypass the SSRF guard and reach internal infrastructure. This issue has been patched in version 1.0.32.