CVE-2026-58197

published 18 Sep 2026 · updated 18 Sep 2026

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

8.8HighCVSS 8.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
stacklok<0.38.0, <0.30.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-58197 severity on Zeptric[![CVE-2026-58197](https://zeptric.io/badge/cve/CVE-2026-58197.svg)](https://zeptric.io/cve/CVE-2026-58197)