CVE-2026-44427

MCP Registry: Open Redirect

N/A

Published: May 14, 2026 at 09:07 PM UTC

Updated: October 26, 2026 at 02:10 PM UTC

1 product affected across 1 vendorMCP Registry

Using registry by modelcontextprotocol?

Get instant alerts when new vulnerabilities affect registry - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.5%

SSVC

PoC

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

MCP Registry · Modelcontextprotocol

90%

1.1.0 ≤ v < 1.7.51.1.0

Affected range stops below 1.7.5, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

x_refsource_CONFIRM

Source: cverecord

https://github.com/modelcontextprotocol/registry/security/advisories/GHSA-v8vw-gw5j-w7m6

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

Quick Info

StatusDEFERRED

CWE

CWE-601

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card