DEV Community

CVE Reports
CVE Reports

Posted on Originally published at cvereports.com

CVE-2026-58197: CVE-2026-58197: Host Escape and Lateral Movement via Insecure Container Network Defaults in ToolHive

CVE-2026-58197: Host Escape and Lateral Movement via Insecure Container Network Defaults in ToolHive

Vulnerability ID: CVE-2026-58197
CVSS Score: 8.8
Published: 2026-09-18

A high-severity access control vulnerability in ToolHive CLI before v0.30.1 and ToolHive Studio before v0.38.0 allows local containerized MCP servers to bypass network isolation. This enables malicious workloads to establish TCP/IP connections to administrative and control plane endpoints exposed on the host loopback interface.

TL;DR

ToolHive failed to isolate local containerized MCP servers by default, allowing malicious containers to bypass isolation via host.docker.internal and access unauthenticated host-local APIs and databases.


Technical Details

  • CWE ID: CWE-284 / CWE-306
  • Attack Vector: Adjacent Network (AV:A)
  • CVSS Base Score: 8.8 (High)
  • Exploit Status: No Public Exploit
  • CISA KEV Status: Not Listed
  • Impact: Privileged Host Access / Remote Code Execution via lateral APIs

Affected Systems

  • ToolHive CLI deployments running containerized MCP servers
  • ToolHive Studio desktop and server installations managing local containers
  • toolhive: < 0.30.1 (Fixed in: v0.30.1)
  • toolhive-studio: < 0.38.0 (Fixed in: v0.38.0)

Code Analysis

Commit: d8f40cb

Fix insecure default network isolation behavior in CLI payloads by using a boolean pointer

Commit: 968182d

Introduce explicit network access profiles and restrict Docker host gateway access in Studio UI

Mitigation Strategies

  • Immediately upgrade ToolHive CLI to v0.30.1 or higher.
  • Immediately upgrade ToolHive Studio to v0.38.0 or higher.
  • Explicitly enforce the --isolate-network=true parameter in all legacy CLI run commands.
  • Implement host-level firewall policies to block Docker bridge networks from connecting to unauthenticated ports on localhost.

Remediation Steps:

  1. Verify the current version of ToolHive CLI by running 'thv --version'.
  2. Download and apply the updated CLI binary (v0.30.1 or greater) from the official repository releases page.
  3. Update ToolHive Studio desktop application to v0.38.0 or greater.
  4. Inspect active containers using 'docker inspect' to ensure that network modes do not permit mapping to host loopback interfaces.
  5. As a temporary workaround, execute all CLI workloads with explicit flags: 'thv run --isolate-network=true '.

References


Read the full report for CVE-2026-58197 on our website for more details including interactive diagrams and full exploit analysis.

Top comments (0)