MCP Registry: Open Redirect
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| modelcontextprotocol | registry | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Modelcontextprotocol | Registry |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-v8vw-gw5j-w7m6 | MCP Registry has open redirect via protocol-relative path in trailing-slash middleware |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.470% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Modelcontextprotocol
Modelcontextprotocol registry |
|
| Vendors & Products |
Modelcontextprotocol
Modelcontextprotocol registry |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | MCP Registry: Open Redirect | |
| Weaknesses | CWE-601 | |
| References |
| |
| Metrics |
cvssV4_0
|