CVE-2026-58197 PUBLISHED

ToolHive: containerized MCP servers can reach host services via host.docker.internal, enabling lateral movement

Assigner: GitHub_M
Reserved: 29.06.2026 Published: 18.09.2026 Updated: 18.09.2026

ToolHive is a utility designed to simplify the deployment and management of Model Context Protocol servers. Prior to ToolHive CLI 0.30.1 and ToolHive Studio 0.38.0, locally run MCP server containers use the default network permission profile without network isolation, permitting access to host.docker.internal while ToolHive API and MCP proxy endpoints are reachable without authentication. A malicious or compromised MCP server can use the Docker gateway to contact host-local services, other ToolHive-managed MCP proxies, or the ToolHive control plane without escaping the container. This access can expose data and logs, invoke sibling MCP tools, alter process or workload state, and disrupt services. ToolHive Studio additionally sends network_isolation as false and overrides the backend's secure isolation default. This issue is fixed in ToolHive CLI 0.30.1 and ToolHive Studio 0.38.0.

Metrics

CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CVSS Score: 8.8

Product Status

Vendor stacklok
Product toolhive
Versions
  • Version < 0.30.1 is affected
Vendor stacklok
Product toolhive-studio
Versions
  • Version < 0.38.0 is affected

References

Problem Types

  • CWE-284: Improper Access Control CWE
  • CWE-306: Missing Authentication for Critical Function CWE