CVE-2026-58197

Overview

ToolHive CLI and Studio before versions 0.30.1 and 0.38.0 run local Model Context Protocol server containers without proper network isolation. This allows unauthenticated access to host-local services, sibling MCP proxies, and the control plane via the Docker gateway. Compromised containers can exploit this lack of segmentation to expose sensitive data, alter workloads, and disrupt services.

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.

Impact

The vulnerability primarily impacts the confidentiality, integrity, and availability of host-local services, container workloads, and the ToolHive control plane. A compromised MCP server can read logs, access sensitive data, invoke unintended sibling tools, and alter operational state without escaping the container boundary. Organizations utilizing default network profiles for local Model Context Protocol deployments are directly exposed to lateral movement and data exfiltration risks.

Remediation

Upgrade ToolHive CLI to version 0.30.1 or later and ToolHive Studio to version 0.38.0 or later to enforce secure network isolation defaults. Ensure that network isolation flags are properly enabled and prevent container access to host.docker.internal where applicable. Audit existing MCP server deployments and review network configuration policies to restrict unauthorized inter-container and host communication.

Risk context

Rated as a high severity vulnerability with a CVSS v3 score of 8.8, indicating significant risk to local environments managing Model Context Protocol servers. Defenders should prioritize patching and configuration reviews to prevent potential lateral movement and unauthorized control plane access.

Affected products

• ToolHive CLI < 0.30.1
• ToolHive Studio < 0.38.0