github.com/modelcontextprotocol/registry vulnerabilities

Registry
Go
Latest
1.8.9

10 known advisories

The latest version, 1.8.9, is not affected by any of them. Projects on older versions may be.

Update to the latest version:go get github.com/modelcontextprotocol/registry@v1.8.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

Security advisories for github.com/modelcontextprotocol/registry

  • 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

Is your github.com/modelcontextprotocol/registry version vulnerable?

Which of your client projects still run an old github.com/modelcontextprotocol/registry?

NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Go packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.