Open Redirect in github.com/modelcontextprotocol/registry (CVE-2026-44427)
Summary
Vulnerability in github.com/modelcontextprotocol/registry (CVE-2026-44427). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.7.5 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44427 has been found in github.com/modelcontextprotocol/registry.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/modelcontextprotocol/registry to 1.7.5 or later.
If unsure, ask your IT team or search "github.com/modelcontextprotocol/registry CVE-2026-44427" on the vendor's site.
CVE-2026-44427 (github.com/modelcontextprotocol/registry) — CWE-601
Patched: 1.7.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-601) exists in github.com/modelcontextprotocol/registry.
Check the vendor advisory for the affected versions of github.com/modelcontextprotocol/registry.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.7.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/modelcontextprotocol/registry' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/modelcontextprotocol/registry' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/modelcontextprotocol/registryを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/modelcontextprotocol/registry to 1.7.5ステージング環境で 1.7.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com