Description
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.
References8
- github.com/stacklok/toolhive-studio/commit/968182d7f3ee1e551233…
- github.com/stacklok/toolhive-studio/pull/2469
- github.com/stacklok/toolhive-studio/releases/tag/v0.38.0
- github.com/stacklok/toolhive/commit/d8f40cb1599b8bf66657f2dfff1…
- github.com/stacklok/toolhive/pull/5583
- github.com/stacklok/toolhive/releases/tag/v0.30.1
- github.com/stacklok/toolhive/security/advisories/GHSA-qg2g-g9w3…
- github.com/stacklok/toolhive/security/advisories/GHSA-qg2g-g9w3…
Metrics
- CVSS 3.1
-
8.8
HIGH
Score source: CNA
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 31 · as of 8 November 2026
- CWE
- CWE-284CWE-306
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.