⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Low · CVSS 2.1

How to Fix CVE-2026-44428: SSRF Vulnerability in registry

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 2.1 - Low
Actively exploited?Not currently listed in CISA KEV
Affected< 1.7.6
Fixed in1.7.6.
Type (CWE)CWE-918: Server-Side Request Forgery (SSRF)

What is CVE-2026-44428?

CVE-2026-44428 is an server-side request forgery (SSRF) flaw in registry. The product makes server-side HTTP requests to attacker-controlled URLs, exposing internal services and cloud metadata endpoints. Vendor description: The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers. Prior to 1.7.6, the client-side and server-side GitHub OIDC flow is bound only to a global audience string, not to the specific registry instance being targeted.

Why this CVE matters

Server-side request forgery routinely chains into cloud-metadata theft, internal service enumeration, and credential exfiltration. In cloud-hosted deployments the impact is often more severe than on-prem because of the metadata service exposure.

For deployments of registry that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open registry's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-44428

  1. Read the vendor advisory in full: https://github.com/modelcontextprotocol/registry/security/advisories/GHSA-95c3-6vvw-4mrq
  2. Upgrade registry to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Apply the Microsoft security update


# CVE-2026-44428 affects registry. Affected build range: < 1.7.6.
# Fixed in build: 1.7.6.
# Vendor advisory: https://github.com/modelcontextprotocol/registry/security/advisories/GHSA-95c3-6vvw-4mrq

# 1. Check the current build on the host.
[System.Environment]::OSVersion.Version
Get-ComputerInfo | Select-Object OsName, OsVersion, OsBuildNumber

# 2. Install the cumulative + security rollup that ships the fix.
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -Confirm:$false
Import-Module PSWindowsUpdate
Get-WindowsUpdate -AcceptAll
Install-WindowsUpdate -AcceptAll -AutoReboot

# 3. Verify the patched build is present.
[System.Environment]::OSVersion.Version
# The build number must be >= 1.7.6 for the patch listed in the advisory.


# Inventory missing patches across a Windows fleet via Ansible (winrm).
ansible windows -m win_updates -a "category_names=SecurityUpdates state=installed"


# Re-run the version check after reboot and log the result.
$log = "C:\Logs\CVE-2026-44428-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
$build = [System.Environment]::OSVersion.Version
"$(Get-Date -Format s) post-patch build: $build" | Out-File $log -Append

Verify the fix landed


# CVE-2026-44428 verification checklist.

# 1. Confirm the running version matches 1.7.6 (replace the version probe with
#    the platform-specific command shown above).

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    OpenVAS, Wazuh). The scanner must no longer flag CVE-2026-44428.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl -u <service-name> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# 4. Cross-check the running build against the vendor advisory:
#    https://github.com/modelcontextprotocol/registry/security/advisories/GHSA-95c3-6vvw-4mrq

If you cannot patch immediately

Block outbound network access from the affected service to internal subnets and cloud metadata endpoints (e.g. 169.254.169.254). Apply the patched build.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unusually long URI paths containing traversal sequences, unexpectedly large responses from the affected endpoint, and outbound requests from the application to internal addresses or cloud-metadata endpoints. Treat any sensitive file the bug could disclose as exposed.

Frequently asked questions

Is CVE-2026-44428 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-44428?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for registry run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*