Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sat, 16 May 2026 01:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 14 May 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | MCP Registry: OCI ownership validation fails open on upstream rate limits, allowing attacker-controlled package claims | |
| Weaknesses | CWE-636 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-16T01:06:38.302Z
Reserved: 2026-05-13T07:45:21.252Z
Link: CVE-2026-45781
Updated: 2026-05-16T01:06:33.365Z
Status : Deferred
Published: 2026-05-14T21:16:48.480
Modified: 2026-05-16T02:16:15.380
Link: CVE-2026-45781
No data.
OpenCVE Enrichment
Updated: 2026-05-14T23:30:31Z