# MCP Registry: OCI validator skips ownership check on upstream rate limits

Advisory record · `GHSA-2v5f-5r6w-p67r`

- **Identifiers:** `GHSA-2v5f-5r6w-p67r` · `CVE-2026-45781` · `GO-2026-5008`
- **State:** Confirmed
- **Severity:** CVSS 3.5 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-636](https://cwe.mitre.org/data/definitions/636.html)
- **Tags:** [CWE-636](https://agentprime.io/advisories/tag/cwe-636.md)
- **Published:** 19 May 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 19 May 2026, 15:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/modelcontextprotocol/registry` (Go): affected `<1.7.9`; fixed in `1.7.9`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Go module github.com/modelcontextprotocol/registry is affected in versions before 1.7.9. When the upstream OCI registry returns HTTP 429 (rate limiting) during package validation, the OCI ownership check is skipped and the publish is accepted. An attacker with a free GitHub account could use this to bind a server record under their own namespace to a public OCI image they do not control. Upgrade to version 1.7.9 or later. The source gives few details on workarounds.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 3.5 Low, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0023, the 14th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:13 UTC: First seen by agentprime
- 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2v5f-5r6w-p67r)

## Sources

- [GitHub Advisory Database: GHSA-2v5f-5r6w-p67r](https://github.com/advisories/GHSA-2v5f-5r6w-p67r)
- [OSV: GHSA-2v5f-5r6w-p67r](https://osv.dev/vulnerability/GHSA-2v5f-5r6w-p67r)
- <https://github.com/modelcontextprotocol/registry/security/advisories/GHSA-2v5f-5r6w-p67r>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-45781>
- <https://github.com/modelcontextprotocol/registry>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-2v5f-5r6w-p67r>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2v5f-5r6w-p67r/>. Everything for agents: <https://agentprime.io/llms.txt>.