Aller au contenu
en Se connecter
3.5 Faible

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

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.

Produits et versions touchés

Produit Versions touchées Corrigé en
registry 1.7 premières → < 1.7.9 1.7.9

Références

Chronologie

  1. Publiée
  2. Dernière modification

Autres CVE de registry

Les 5 CVE de registry →
CVE-2026-44428 The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers 2.1 Faible CVE-2026-44427 The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers 0.0 Non notée CVE-2026-44429 The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers 5.1 Moyenne CVE-2026-44430 The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers 6.3 Moyenne
Suivre cette CVE