Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-v8vw-gw5j-w7m6 | MCP Registry has open redirect via protocol-relative path in trailing-slash middleware |
Fri, 15 May 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 14 May 2026 21:45:00 +0000
| 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
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-15T13:33:16.949Z
Reserved: 2026-05-06T14:40:00.953Z
Link: CVE-2026-44427
Updated: 2026-05-15T13:33:00.617Z
Status : Deferred
Published: 2026-05-14T22:16:44.450
Modified: 2026-05-15T15:16:52.670
Link: CVE-2026-44427
No data.
OpenCVE Enrichment
Updated: 2026-05-14T22:30:25Z
Github GHSA