CVE-2026-44427: MCP Registry has open redirect via protocol-relative path in trailing-slash middleware
Summary The TrailingSlashMiddleware in internal/api/server.go is vulnerable to an open redirect attack. An attacker can craft a URL with a protocol-relative path (e.g., //evil.com/) that, after trailing slash removal, results in a Location header of //evil.com — which browsers interpret as an absolute URL to an external domain.
Published May 8, 2026 · Updated May 15, 2026
Affected packages
github.com/modelcontextprotocol/registry
- Ecosystem
- Go
- Affected
- >= 1.1.0, < 1.7.5
- Fixed in
- 1.7.5
- Check
go list -m github.com/modelcontextprotocol/registry
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The TrailingSlashMiddleware in internal/api/server.go is vulnerable to an open redirect attack. An attacker can craft a URL with a protocol-relative path (e.g., //evil.com/) that, after trailing slash removal, results in a Location header of //evil.com — which browsers interpret as an absolute URL to an external domain.
Details
The TrailingSlashMiddleware strips trailing slashes from request paths and issues a 308 Permanent Redirect to the cleaned path. However, it does not validate or sanitize the resulting path before using it as the redirect target.
When a request is made with a path like //evil.com/, the middleware processes it as follows:
PoC
- Start the registry server locally or identify a deployed instance
- Send a request with a double-slash path followed by an external domain:
curl -v https://<registry-host>//evil.com/
- Observe the 308 Permanent Redirect response with Location: //evil.com:
- When accessed in a browser, the user is redirected to https://evil.com
Impact
Phishing: Attackers can abuse the trusted registry domain to redirect users to credential-harvesting pages Malware distribution: Redirect users to sites serving malicious downloads Trust abuse: Links originating from the official MCP Registry domain carry implicit trust
Credited to gujasec, rdimitrov.
References
- https://github.com/modelcontextprotocol/registry/security/advisories/GHSA-v8vw-gw5j-w7m6
- https://github.com/modelcontextprotocol/registry/pull/1227
- https://github.com/modelcontextprotocol/registry/commit/1201cbd82b2cf6d4b56edfc05c763059a12f9fdb
- https://github.com/modelcontextprotocol/registry/releases/tag/v1.7.5
- https://nvd.nist.gov/vuln/detail/CVE-2026-44427
- https://github.com/advisories/GHSA-v8vw-gw5j-w7m6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-45781
MCP Registry: OCI validator skips ownership check on upstream rate limits
low3.5May 19, 2026CVE-2026-44428
MCP Registry's GitHub OIDC tokens are replayable across registry deployments due to shared audience
low4.7May 8, 2026CVE-2026-44429
MCP Registry vulnerable to stored XSS in catalogue UI via attribute-quote breakout in publisher-controlled `websiteUrl`
medium5.4May 8, 2026CVE-2026-44430
MCP Registry has an unauthenticated SSRF: HTTP namespace verification dials 6to4 / NAT64 / site-local IPv6 addresses, bypassing private-address allowlist
medium4.0May 8, 2026
