ToolHive is a utility designed to simplify the deployment and management of Model Context Protocol (MCP) servers. Prior to 0.31.0, remote.Handler.Authenticate in pkg/auth/remote/handler.go invokes discovery.DetectAuthenticationFromServer in pkg/auth/discovery/discovery.go, whose host-side HTTP clients trust remote-server-controlled authentication discovery destinations, follow redirects without host or scheme restrictions, and do not consistently block private addresses. A malicious or compromised remote MCP server can place a resource_metadata URL in WWW-Authenticate for ParseWWWAuthenticate to extract, after which FetchResourceMetadata, OIDC issuer discovery, and well-known discovery can issue GET requests to link-local, RFC1918, or other internal services outside the server's container. The user connects to a server that the user intends to use, but the server controls the internal destination; this path does not depend on the separate NAT64 guard omission because the affected clients did not invoke IsPrivateIP, and it differs from the DCR resolver path that already refused redirects. The demonstrated primitive reaches internal-only HTTP services and reachability or error oracles, and can retrieve AWS metadata credentials where IMDSv1 accepts an unauthenticated GET, while IMDSv2 and GCP metadata prerequisites are not satisfied by the demonstrated request. This vulnerability is fixed in 0.31.0.
CVE-2026-58196
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 4.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 4.7
- EG Score
- 4.7MEDIUMmedium confidence
- EG Risk
- 37EG Risk 37/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity47% × 45%The EG Score, 4.7 of 10.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 35th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
July 15, 2026
Last Modified
September 30, 2026
Advisory Details (3)
Auto-updated Sep 15, 2026v0.31.0
Patch available: stacklok/toolhive v0.31.0
https://github.com/stacklok/toolhive/releases/tag/v0.31.0commit 4ea6afb9048d (stacklok/toolhive)
Fix landed in stacklok/toolhive commit 4ea6afb9048d — awaiting tagged release
https://github.com/stacklok/toolhive/commit/4ea6afb9048ddec1d56875fa9e0da36d65c15966SSRF in remote MCP server authentication discovery (host-side, bypasses container isolation) · Advisory · stacklok/toolhive · GitHub
https://github.com/stacklok/toolhive/security/advisories/GHSA-pr64-jmmf-jp54Vendor Advisories for CVE-2026-58196(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/stacklok/toolhive | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 37× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-12 15:53 UTCEG score recompute
- 2026-10-11 19:36 UTCEG score recompute
- 2026-10-11 16:52 UTCEG score recompute
- 2026-10-11 14:14 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-30 18:11 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-28 08:40 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 16 moreShow fewer
- 2026-09-24 08:45 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-23 03:12 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-18 04:42 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-15 18:36 UTCEG score recompute
- 2026-09-15 18:14 UTCEG score recompute
- 2026-09-15 16:35 UTCEG score recompute
- 2026-09-15 16:02 UTCMITRE cvelistV5severity → MEDIUM
- 2026-07-31 00:48 UTCEG score recompute
- 2026-07-26 11:28 UTCEG score recompute
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-15 23:54 UTCEG score recompute
Related CVEs(same product + same CWE)
Frequently asked(5)
What is CVE-2026-58196?
When was the CVE record for CVE-2026-58196 published?
Is CVE-2026-58196 actively exploited?
What is the CVSS score of CVE-2026-58196?
How do I remediate CVE-2026-58196?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58196
Is Your Infrastructure Affected by CVE-2026-58196?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.