None severity · published May 14, 2026
CVE-2026-44427
MCP Registry: Open Redirect
0.0
CVSS
0.5%
EPSS
No
On KEV
Description
The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers. From 1.1.0 to 1.7.4, 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. This vulnerability is fixed in 1.7.5.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.5% · higher than 40% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
RE
registry · modelcontextprotocol
>= 1.1.0, < 1.7.5 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-44427
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-44427
github.com
https://github.com/modelcontextprotocol/registry/security/advisories/GHSA-v8vw-gw5j-w7m6
More from registry
5.4
CVE-2026-44429
MCP Registry: Stored XSS in catalogue UI via attribute-quote breakout in publisher-controlled `websiteUrl`
4.7
CVE-2026-44428
MCP Registry: GitHub OIDC tokens replayable across registry deployments due to shared audience
4.0
CVE-2026-44430
MCP Registry: Unauthenticated SSRF: HTTP namespace verification dials 6to4 / NAT64 / site-local IPv6 addresses, bypassing private-address allowlist
3.5
CVE-2026-45781
MCP Registry: OCI ownership validation fails open on upstream rate limits, allowing attacker-controlled package claims