Approved changes feed: RSS · Atom

cpe:2.3:a:stacklok:toolhive-studio:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorStacklok (143141ff-e25a-5851-8633-8bff8193e1ec)
ProductToolhive Studio (896102e3-eb0b-528a-a677-c3ac283f25b7)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-58197 vulnerable 2026-10-13 12:28:31.846664 ToolHive: containerized MCP servers can reach host services via host.docker.internal, enabling lateral movement
HIGH (8.8)
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.
Published: 2026-09-18T16:34:55.213Z
Updated: 2026-09-18T16:51:27.459Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.