Most recent entries from all

EUVD-2026-319122

2026-10-06T23:03:23.670330+00:00

EUVD-2026-319122

fkie_cve-2026-45781

2026-10-06T23:03:23.670367+00:00

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./* 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.

GHSA-2v5f-5r6w-p67r — MCP Registry: OCI validator skips ownership check on upstream rate limits

2026-10-06T23:03:23.670410+00:00

Affected: Go: github.com/modelcontextprotocol/registry

# OCI ownership validation fails open on upstream rate limits, allowing attacker to claim arbitrary public OCI images under their own namespace

Severity: Low (re-scored post-triage; see Maintainer triage note below) Affected: `modelcontextprotocol/registry` main branch at commit `fe0cb3b` (current HEAD as of 2026-05-09). Live deployment: `https://registry.modelcontextprotocol.io` (per repo README). Route: GitHub private security advisory (per repo SECURITY.md).

---

## Title

OCI ownership validation skips label-match check when upstream OCI registry returns HTTP 429, letting any authenticated publisher bind their `io.github./*` namespace to OCI images they do not control.

## Summary

`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.

The fail-open trigger is attacker-controllable. The registry uses `authn.Anonymous` against Docker Hub, which is rate-limited to 100 manifest pulls per 6 hours per egress IP, and the production NGINX rate limit allows 180 publishes/minute (3 RPS, burst 540) per sour…