MCP Registry: Open Redirect
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-44427
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 18:30 UTC · Revision 1
Source evidence
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.
osv:CVE-2026-44427
Complete source record
{
"id": "be9f203affbce2d498403efc2ee95de1f598b729131bd81cee79183baefbf06a",
"url": "https://osv.dev/vulnerability/CVE-2026-44427",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "MCP Registry: Open Redirect",
"summary": "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.",
"evidence": "osv:CVE-2026-44427",
"products": [],
"severity": "unknown",
"structured": {
"id": "CVE-2026-44427",
"aliases": [
"CVE-2026-44427",
"GHSA-v8vw-gw5j-w7m6",
"GO-2026-5658"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/modelcontextprotocol/registry",
"type": "GIT",
"events": [
{
"introduced": "ae00f70eaf2202970d74f5d459fd174ab8445a8a"
},
{
"fixed": "1201cbd82b2cf6d4b56edfc05c763059a12f9fdb"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "1.1.0"
},
{
"fixed": "1.7.5"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"introduced": "0"
},
{
"fixed": "1.7.5"
}
],
"source": "DESCRIPTION"
}
]
}
}
],
"versions": [
"v1.7.4",
"v1.7.3",
"v1.7.2",
"v1.7.1",
"v1.7.0",
"v1.6.0",
"v1.5.0",
"v1.4.1",
"v1.4.0",
"v1.3.10",
"v1.3.9",
"v1.3.8",
"v1.3.7",
"v1.3.6",
"v1.3.5",
"v1.3.4",
"v1.3.3",
"v1.3.2",
"v1.3.1",
"v1.3.0",
"v1.2.3",
"v1.2.2",
"v1.2.1",
"v1.2.0",
"v1.1.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-44427.json"
}
}
],
"modified": "2026-10-28T02:30:38.291920256Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/44xxx/CVE-2026-44427.json",
"https://github.com/modelcontextprotocol/registry/security/advisories/GHSA-v8vw-gw5j-w7m6",
"https://nvd.nist.gov/vuln/detail/CVE-2026-44427"
],
"provider_metadata": {
"cwe_ids": [
"CWE-601"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/44xxx/CVE-2026-44427.json"
}
},
"related_cves": [
{
"value": "CVE-2026-44427",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 505715,
"published_at": "2026-05-14T21:07:34.364+00:00"
}