MCP Registry has an unauthenticated SSRF: HTTP namespace verification dials 6to4 / NAT64 / site-local IPv6 addresses, bypassing private-addr
CVE-2026-44430 · GHSA-r48c-v28r-pf6v · published 2026-05-08 · updated 2026-05-15
- Severity
- Medium
- CVSS score
- 4.0
- Chance of exploitation (EPSS)
- 0.29%
- Fixed in
- 1.7.7
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
CWE: CWE-918 Server-Side Request Forgery (consistent with parent precedent GHSA-56c3-vfp2-5qqj). CVSS:3.1: matching the n8n-mcp precedent (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N ~= 8.5 HIGH). AC = High because exploitation depends on the registry host having NAT64 or 6to4 routing — the default on IPv6-only and dual-stack cloud network plans (GKE IPv6, AWS IPv6-only EC2, Azure IPv6 VMs with NAT64) but not on plain-IPv4 deployments. Privileges = None (the endpoint is the login flow itself).
Upgrade github.com/modelcontextprotocol/registry to 1.7.7 or later.
isBlockedIP should return true for any IPv6 address in the prefix families listed above, mirroring the n8n-mcp isPrivateOrMappedIpv6 helper (GHSA-56c3-vfp2-5qqj patch). Reference implementation: Then extend the call site: A regression test fixture should set up a stub resolver returning each of the four prefix families and assert that safeDialContext returns the "private/loopback" error before any dial.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| github.com/modelcontextprotocol/registry | Go | < 1.7.7 | 1.7.7 |
- CriticalMLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebindingmlflowExploited
- Critical@zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery@zereight/mcp-gitlab
- CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
- CriticalLocalAI POST /models/apply permits unauthenticated server-side request forgery through gallery URLsgithub.com/mudler/LocalAI
- CriticalFastMCP OpenAPI Provider has an SSRF & Path Traversal Vulnerabilityfastmcp
- CriticalBentoML SSRF Vulnerability in File Upload Processingbentoml
- MediumMCP Registry vulnerable to stored XSS in catalogue UI via attribute-quote breakout in publisher-controlled `websiteUrl`github.com/modelcontextprotocol/registry
- MediumMCP Registry has open redirect via protocol-relative path in trailing-slash middlewaregithub.com/modelcontextprotocol/registry
- LowMCP Registry: OCI validator skips ownership check on upstream rate limitsgithub.com/modelcontextprotocol/registry
- LowMCP Registry's GitHub OIDC tokens are replayable across registry deployments due to shared audiencegithub.com/modelcontextprotocol/registry
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.