mcp-fetch checks a fetch target against its SSRF guard without removing the brackets that surround an IPv6 literal. isSafeUrl reads the hostname from the parsed URL, which for a literal such as http://[::1]/ yields the bracketed string, and then tests it with net.isIP. That call returns zero for a bracketed value, so the branch holding the private-address checks is skipped entirely. The guard falls back to resolving the hostname, the bracketed string is not a resolvable name, no addresses are returned, and the target is reported safe. The HTTP client then strips the brackets and connects. Because the address may be given in IPv4-mapped form, the same path reaches any IPv4 target the loopback and private checks were meant to exclude, including link-local metadata endpoints. isPrivateIPv6 also has no case for the ::ffff: prefix, so the mapped form would still pass even if the brackets were removed. The fetch target is supplied as a tool argument, so an attacker who can influence what the model requests can read internal responses back into the model context.
CVE-2026-80347
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
August 26, 2026
Last Modified
August 26, 2026
Advisory Details (3)
Auto-updated Aug 26, 2026mcp-fetch through 1.6.3 Server-Side Request Forgery via Unstripped IPv6 Literal Brackets | Advisories | VulnCheck
https://www.vulncheck.com/advisories/mcp-fetch-through-1.6.3-server-side-request-forgery-via-unstripped-ipv6-literal-bracketsSSRF guard bypass via IPv6 literal (brackets not stripped before net.isIP) · Issue #16 · kazuph/mcp-fetch · GitHub
https://github.com/kazuph/mcp-fetch/issues/16Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-08-30 05:43 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 05:17 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 16:25 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 15:54 UTCEG score recompute
- 2026-08-26 12:19 UTCEG score recompute
- 2026-08-26 10:18 UTCEG score recompute
- 2026-08-26 10:17 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-80347?
When was CVE-2026-80347 disclosed?
Is CVE-2026-80347 actively exploited?
What is the CVSS score of CVE-2026-80347?
How do I remediate CVE-2026-80347?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-80347
Is Your Infrastructure Affected by CVE-2026-80347?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.