CVE-2026-44430: The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers

Q: How do I fix CVE-2026-44430?

mcp registry: upgrade to 1.7.7. Exact commands for each OS are on this page.

Q: Is CVE-2026-44430 being exploited?

CVE-2026-44430 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-44430 affect?

CVE-2026-44430 affects mcp registry. Severity is medium (CVSS 4.0). The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers. Prior to 1.7.7, the Registry's HTTP-based namespace verification (POST /v0/auth/http, POST /v0.1/auth/http) uses safeDialContext (internal/

Q: How urgent is CVE-2026-44430?

Priority 29/100. Public exploit reference; Remotely exploitable, no login, no user action

This week

MEDIUM 4.0REMOTEUPGRADE

CVE-2026-44430 is a medium-severity flaw (CVSS 4.0) affecting mcp registry. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers. Prior to 1.7.7, the Registry's HTTP-based namespace verification (POST /v0/auth/http, POST /v0.1/auth/http) uses safeDialContext (internal/api/handlers/v0/auth/http.go:67-110) to refuse dialling private/internal addresses when fetching the well-known public-key file from a publisher-supplied domain. The blocklist (isBlockedIP, lines 125-133) relie

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	4.0 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 79%)
CISA exploited list	No
Weakness	CWE-918
Published	2026-05-14
Last modified	2026-10-26

Publisher (CNA): GitHub, Inc. · Vendor: lfprojects

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-14 21:16 UTCPublished CVE record published
2026-10-26 14:10 UTCUpdated Record last modified

lfprojects mcp registry UPGRADE

Affected: < 1.7.7

Fixed in: 1.7.7

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy mcp-registry || rpm -q mcp-registry || mcp-registry --version

2. UPGRADE to 1.7.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade mcp-registry

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade mcp-registry

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-44430?

mcp registry: upgrade to 1.7.7. Exact commands for each OS are on this page.

Is CVE-2026-44430 being exploited?

CVE-2026-44430 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-44430 affect?

CVE-2026-44430 affects mcp registry. Severity is medium (CVSS 4.0). The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers. Prior to 1.7.7, the Registry's HTTP-based namespace verification (POST /v0/auth/http, POST /v0.1/auth/http) uses safeDialContext (internal/

How urgent is CVE-2026-44430?

Priority 29/100. Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-44429 MEDIUM 5.4 UPGRADE The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers
CVE-2026-44428 MEDIUM 4.7 UPGRADE The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers

References

← Back to latest CVEs