Is CVE-2026-45781 actively exploited?

No active exploitation of CVE-2026-45781 has been confirmed so far. Continue monitoring, as exploit status can change.

Can CVE-2026-45781 be exploited remotely?

Yes. CVE-2026-45781 is exploitable remotely over the network (CVSS attack vector: Network).

What is the CVSS score of CVE-2026-45781?

CVE-2026-45781 has a CVSS score of 3.5 (LOW).

HOME VULNERABILITIESCVE-2026-45781

LOW

CVE-2026-45781

CWE-636Published: May 14, 2026· Updated: May 16, 2026

3.5

CVSS v3.1

EPSS:0.03%probability of exploitation in 30 daysPercentile:8.3th

Official Description

The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers. Prior to 1.7.9, OCI ownership validation skips label-match check when upstream OCI registry returns HTTP 429, letting any authenticated publisher bind their io.github.<user>/* namespace to OCI images they do not control. internal/validators/registries/oci.go:104-119 fails open on http.StatusTooManyRequests: when the registry's anonymous fetch to the upstream OCI registry is rate-limited, ValidateOCI returns nil and the publish is accepted without ever running the io.modelcontextprotocol.server.name label-match check at lines 122-141. That label check is the only cross-system ownership proof the registry applies to OCI packages — every other registry type (NPM, PyPI, NuGet, MCPB) treats a non-200 upstream response as a hard error. This vulnerability is fixed in 1.7.9.

NVD Source

Technical Analysis

CVE-2026-45781 can be exploited remotely over the network without requiring physical or adjacent access, significantly expanding the attack surface for threat actors.

Exploitation requires low privileges, which limits the exposure to scenarios where an attacker has already gained initial access.