← Back
CVE-2026-44428
SSRF (Server-Side Request Forgery) in github.com/modelcontextprotocol/registry (CVE-2026-44428)
Summary
SSRF in github.com/modelcontextprotocol/registry (CVE-2026-44428). Risk of unauthorized operations or information disclosure. Exploitable via ``c5c4b9e8890dd5754bee889b2f1417f4fe3b5ce5``. Mitigation: upgrade to `1.7.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44428** has been found in github.com/modelcontextprotocol/registry.
Attackers can target a specific entry point like ``c5c4b9e8890dd5754bee889b2f1417f4fe3b5ce5`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/modelcontextprotocol/registry to **1.7.6** or later.
If unsure, ask your IT team or search "github.com/modelcontextprotocol/registry CVE-2026-44428" on the vendor's site.
CVE-2026-44428 (github.com/modelcontextprotocol/registry) — CWE-918 /
Attack surface: `c5c4b9e8890dd5754bee889b2f1417f4fe3b5ce5` / `repository_owner` / `flags.RegistryURL` / `GitHubOIDCProvider`
Patched: `1.7.6` — 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.
❓ What is the problem
**SSRF** (CWE-918) exists in github.com/modelcontextprotocol/registry. Attackers reach the vulnerable code path via ``c5c4b9e8890dd5754bee889b2f1417f4fe3b5ce5`` without authentication.
📍 Affected scope
github.com/modelcontextprotocol/registry — . Attack surface: `c5c4b9e8890dd5754bee889b2f1417f4fe3b5ce5` / `repository_owner` / `flags.RegistryURL` / `GitHubOIDCProvider`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.7.6**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/modelcontextprotocol/registry to 1.7.6ステージング環境で 1.7.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/modelcontextprotocol/registry
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.6"}]}]
References
- web https://github.com/modelcontextprotocol/registry/security/advisories/GHSA-95c3-6vvw-4mrq
- web https://github.com/modelcontextprotocol/registry/pull/1229
- web https://github.com/modelcontextprotocol/registry/commit/3f89fc2b1fb34fd49f3c0e1b39e964a5c67b613f
- web https://github.com/modelcontextprotocol/registry/releases/tag/v1.7.6
- web https://github.com/advisories/GHSA-95c3-6vvw-4mrq