modelcontextprotocol registry up to 1.7.4 internal/api/server.go TrailingSlashMiddleware redirect

Summaryinfo

A vulnerability classified as problematic has been found in modelcontextprotocol registry up to 1.7.4. Affected by this issue is the function TrailingSlashMiddleware of the file internal/api/server.go. The manipulation leads to redirect. This vulnerability is listed as CVE-2026-44427. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in modelcontextprotocol registry up to 1.7.4. It has been rated as problematic. This issue affects the function TrailingSlashMiddleware of the file internal/api/server.go. The manipulation with an unknown input leads to a redirect vulnerability. Using CWE to declare the problem leads to CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. Impacted is integrity. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-44427 since 05/06/2026. The exploitation is known to be easy. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1204.001 for this issue.

Upgrading to version 1.7.5 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• modelcontextprotocol

Name

• registry

Version

• 1.7.0
• 1.7.1
• 1.7.2
• 1.7.3
• 1.7.4

Website

• Product: https://github.com/modelcontextprotocol/registry/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion