Lateral movement via unisolated container networking
Published Sep 18, 2026 · Updated Sep 18, 2026
Improper network isolation in ToolHive before 0.30.1 and ToolHive Studio before 0.38.0 allows attackers to access host services. The default network profile permits host.docker.internal, while Studio sends network_isolation as false and overrides the secure backend default. A malicious or compromised MCP server can call unauthenticated APIs and sibling proxies to read data, invoke tools, alter workloads, or interrupt services.
Summary
What happened
Improper network isolation in ToolHive before 0.30.1 and ToolHive Studio before 0.38.0 allows attackers to access host services. The default network profile permits host.docker.internal, while Studio sends network_isolation as false and overrides the secure backend default. A malicious or compromised MCP server can call unauthenticated APIs and sibling proxies to read data, invoke tools, alter workloads, or interrupt services.
The record
- CVE
- CVE-2026-58197
- Published
- Sep 18, 2026
- Updated
- Sep 18, 2026
- Vendor
- Stacklok
- Product
- ToolHive
- Classifications
- T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.30.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Upstream host.docker.internal reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started