Is github.com/modelcontextprotocol/registry 1.7 vulnerable?

Go · 10 releases from 1.7.0 to 1.7.9 · latest github.com/modelcontextprotocol/registry is 1.8.9 · checked 18 Nov 2026

No known advisories in the last release

github.com/modelcontextprotocol/registry 1.7.9, the last 1.7 release, has no known advisories. 10 advisories affect earlier 1.7.x releases, so update to 1.7.9.

Update within 1.7:go get github.com/modelcontextprotocol/registry@v1.7.9

Is your project on an affected github.com/modelcontextprotocol/registry?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 1.7.x, affecting earlier releases

  • LowCVE-2026-44429GO-2026-563725 Jun 2026

    MCP Registry vulnerable to stored XSS in catalogue UI via attribute-quote breakout in publisher-controlled `websiteUrl` in github.com/modelcontextprotocol/registry

    Affected
    <1.7.7
    Fixed in
    1.7.7
  • LowCVE-2026-44427GO-2026-565825 Jun 2026

    MCP Registry has open redirect via protocol-relative path in trailing-slash middleware in github.com/modelcontextprotocol/registry

    Affected
    >=1.1.0 <1.7.5
    Fixed in
    1.7.5
  • LowCVE-2026-44430GO-2026-560725 Jun 2026

    MCP Registry has an unauthenticated SSRF: HTTP namespace verification dials 6to4 / NAT64 / site-local IPv6 addresses, bypassing private-address allowlist in github.com/modelcontextprotocol/registry

    Affected
    <1.7.7
    Fixed in
    1.7.7
  • LowCVE-2026-44428GO-2026-527325 Jun 2026

    MCP Registry's GitHub OIDC tokens are replayable across registry deployments due to shared audience in github.com/modelcontextprotocol/registry

    Affected
    <1.7.6
    Fixed in
    1.7.6
  • LowCVE-2026-45781GO-2026-500820 May 2026

    MCP Registry: OCI validator skips ownership check on upstream rate limits in github.com/modelcontextprotocol/registry

    Affected
    <1.7.9
    Fixed in
    1.7.9
  • LowCVE-2026-45781GHSA-2v5f-5r6w-p67r19 May 2026

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

    Affected
    <1.7.9
    Fixed in
    1.7.9
  • MediumCVE-2026-44430GHSA-r48c-v28r-pf6v8 May 2026

    MCP Registry has an unauthenticated SSRF: HTTP namespace verification dials 6to4 / NAT64 / site-local IPv6 addresses, bypassing private-address allowlist

    Affected
    <1.7.7
    Fixed in
    1.7.7
  • MediumCVE-2026-44429GHSA-rqv2-m695-f8j48 May 2026

    MCP Registry vulnerable to stored XSS in catalogue UI via attribute-quote breakout in publisher-controlled `websiteUrl`

    Affected
    <1.7.7
    Fixed in
    1.7.7
  • LowCVE-2026-44428GHSA-95c3-6vvw-4mrq8 May 2026

    MCP Registry's GitHub OIDC tokens are replayable across registry deployments due to shared audience

    Affected
    <1.7.6
    Fixed in
    1.7.6
  • MediumCVE-2026-44427GHSA-v8vw-gw5j-w7m68 May 2026

    MCP Registry has open redirect via protocol-relative path in trailing-slash middleware

    Affected
    >=1.1.0 <1.7.5
    Fixed in
    1.7.5

Every github.com/modelcontextprotocol/registry 1.7.x release

Affected: 1.7.0 to 1.7.8. 1.7.9 is not affected. Latest github.com/modelcontextprotocol/registry: 1.8.9.

VersionKnown advisories
github.com/modelcontextprotocol/registry 1.7.9None
github.com/modelcontextprotocol/registry 1.7.8CVE-2026-45781, CVE-2026-45781
github.com/modelcontextprotocol/registry 1.7.7CVE-2026-45781, CVE-2026-45781
github.com/modelcontextprotocol/registry 1.7.6CVE-2026-44429, CVE-2026-44430, CVE-2026-45781, CVE-2026-45781, CVE-2026-44430, CVE-2026-44429
github.com/modelcontextprotocol/registry 1.7.5CVE-2026-44429, CVE-2026-44430, CVE-2026-44428, CVE-2026-45781, CVE-2026-45781, CVE-2026-44430, CVE-2026-44429, CVE-2026-44428
github.com/modelcontextprotocol/registry 1.7.4CVE-2026-44429, CVE-2026-44427, CVE-2026-44430, CVE-2026-44428, CVE-2026-45781, CVE-2026-45781, CVE-2026-44430, CVE-2026-44429, CVE-2026-44428, CVE-2026-44427
github.com/modelcontextprotocol/registry 1.7.3CVE-2026-44429, CVE-2026-44427, CVE-2026-44430, CVE-2026-44428, CVE-2026-45781, CVE-2026-45781, CVE-2026-44430, CVE-2026-44429, CVE-2026-44428, CVE-2026-44427
github.com/modelcontextprotocol/registry 1.7.2CVE-2026-44429, CVE-2026-44427, CVE-2026-44430, CVE-2026-44428, CVE-2026-45781, CVE-2026-45781, CVE-2026-44430, CVE-2026-44429, CVE-2026-44428, CVE-2026-44427
github.com/modelcontextprotocol/registry 1.7.1CVE-2026-44429, CVE-2026-44427, CVE-2026-44430, CVE-2026-44428, CVE-2026-45781, CVE-2026-45781, CVE-2026-44430, CVE-2026-44429, CVE-2026-44428, CVE-2026-44427
github.com/modelcontextprotocol/registry 1.7.0CVE-2026-44429, CVE-2026-44427, CVE-2026-44430, CVE-2026-44428, CVE-2026-45781, CVE-2026-45781, CVE-2026-44430, CVE-2026-44429, CVE-2026-44428, CVE-2026-44427

Which of your client projects are still on github.com/modelcontextprotocol/registry 1.7?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/modelcontextprotocol/registry version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other github.com/modelcontextprotocol/registry versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.