CVE-2026-79743: MCPHub: Path Traversal via Malicious MCPB Manifest Name
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 0.12.13, MCPB File Upload Handler extracts a ZIP file and reads manifest.json from it. The name field in the manifest is directly concatenated into a file path (line 107) without any sanitization or path traversal character validation. An attacker can craft a malicious MCPB file where manifest.name is set to something like ../../../etc/malicious, causing the file to be extracted to an arbitrary location on the file system. The cleanupOldMcpbServer function (line 110) also uses the unsanitized name, potentially allowing deletion of arbitrary directories. This issue has been patched in version 0.12.13.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
MCPHubto a version that resolves this vulnerability.Fixed in 0.12.13
Event History
Frequently Asked Questions
Which deployments are affected?
MCPHub deployments running versions prior to 0.12.13 are affected where the MCPB File Upload Handler processes uploaded MCPB files.
What does an attacker need to exploit this issue?
An attacker needs to provide a crafted MCPB ZIP file with a manifest.json whose name field contains path traversal sequences. The vulnerable upload handler uses that name in file paths without sanitization.
What can exploitation do?
A crafted manifest name can cause files to be extracted to arbitrary filesystem locations. The same unsanitized value is used by cleanupOldMcpbServer, which can potentially delete arbitrary directories.
What should be done if the deployment cannot be upgraded immediately?
Do not process untrusted MCPB uploads until the deployment can be updated. Restricting MCPB upload capability to trusted users reduces the opportunity to submit a malicious manifest.
How is the issue remediated?
Upgrade MCPHub to version 0.12.13, which includes the patch for this issue.