CVE-2026-44430: modelcontextprotocol registry · Server-Side Request Forgery (SSRF)
Affects modelcontextprotocol registrySource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.7.7 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.7.7
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 14 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade registry and modelcontextprotocol/registry to 1.7.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| modelcontextprotocolregistry | Affected
| Fixed in
|
GitHubmodelcontextprotocol/registrypkg:github/modelcontextprotocol/registryOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the modelcontextprotocol registry to version 1.7.7 or later, where this vulnerability is fixed. Patch status is not explicitly stated in the vendor advisory, but the description confirms the issue is resolved in 1.7.7. Until upgrading, be aware that the IP blocklist does not cover certain IPv6 ranges, which can be exploited for SSRF.
Description
CVE-2026-44430 is a Server-Side Request Forgery (SSRF) vulnerability in the modelcontextprotocol (MCP) registry versions prior to 1.7.7. The vulnerability arises because the registry's HTTP-based namespace verification uses a blocklist that does not cover certain IPv6 address ranges (6to4, NAT64, and deprecated site-local), which can encode arbitrary IPv4 addresses. This allows an attacker to bypass restrictions intended to prevent dialing private or internal addresses, potentially enabling SSRF attacks. The issue is fixed in version 1.7.7.