# ToolHive: containerized MCP servers can reach host services via host.docker.internal, enabling lateral movement Advisory record · `GHSA-qg2g-g9w3-m5h8` - **Identifiers:** `GHSA-qg2g-g9w3-m5h8` · `CVE-2026-58197` · `GO-2026-6526` - **State:** Confirmed - **Severity:** CVSS 8.8 High - **Critical:** No - **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html) · [CWE-306](https://cwe.mitre.org/data/definitions/306.html) - **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) - **Published:** 18 Sept 2026 - **Updated:** 28 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 18 Sept 2026, 17:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/stacklok/toolhive` (Go): affected `<0.30.1`; fixed in `0.30.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > ToolHive (Go module github.com/stacklok/toolhive) versions before 0.30.1 are affected. A containerized MCP server using the default network permission profile can reach host-local services through host.docker.internal, including the ToolHive API and other MCP server proxies, which lack authentication. An attacker who controls or compromises such a container could move laterally to the host and other services without a container escape. Upgrade to version 0.30.1 or later. The source gives few details on workarounds. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 8.8 High, CVSS 3.1: `CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0037, the 31st percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:12 UTC: First seen by agentprime - 31 Oct 2026, 14:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qg2g-g9w3-m5h8) ## Sources - [GitHub Advisory Database: GHSA-qg2g-g9w3-m5h8](https://github.com/advisories/GHSA-qg2g-g9w3-m5h8) - [OSV: GHSA-qg2g-g9w3-m5h8](https://osv.dev/vulnerability/GHSA-qg2g-g9w3-m5h8) - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .