CVE-2026-45781
- Source
- https://cve.org/CVERecord?id=CVE-2026-45781
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-45781.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-45781
- Aliases
- Related
- Published
- 2026-05-14T21:00:49.961Z
- Modified
- 2026-07-08T08:13:31.464555365Z
- Severity
-
- 3.5 (Low) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N CVSS Calculator
- Summary
- MCP Registry: OCI ownership validation fails open on upstream rate limits, allowing attacker-controlled package claims
- Details
-
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.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/45xxx/CVE-2026-45781.json", "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-636" ] }- References