External redirects via unsanitized protocol-relative paths
Published May 14, 2026 · Updated May 14, 2026
Open redirect in MCP Registry 1.1.0 through 1.7.4 allows remote attackers to send users to external sites via crafted URLs. TrailingSlashMiddleware in internal/api/server.go trims a trailing slash and places the unvalidated protocol-relative path into a 308 Location header, which browsers resolve off-host. Exploitation requires a user to follow the crafted registry link; the redirect supports phishing or malicious-download delivery without changing registry data.
Summary
What happened
Open redirect in MCP Registry 1.1.0 through 1.7.4 allows remote attackers to send users to external sites via crafted URLs. TrailingSlashMiddleware in internal/api/server.go trims a trailing slash and places the unvalidated protocol-relative path into a 308 Location header, which browsers resolve off-host. Exploitation requires a user to follow the crafted registry link; the redirect supports phishing or malicious-download delivery without changing registry data.
The record
- CVE
- CVE-2026-44427
- Published
- May 14, 2026
- Updated
- May 14, 2026
- Vendor
- Model Context Protocol
- Product
- MCP Registry
- Classifications
- CWE-601, T1566.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2026CVE publishedPublication date reported by the CVE source.
- May 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.1.0, < 1.7.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream protocol-relative redirect proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo