Is github.com/modelcontextprotocol/registry 0.0 vulnerable?
Go · 3 releases from 0.0.1 to 0.0.3 · latest github.com/modelcontextprotocol/registry is 1.8.9 · checked 18 Nov 2026
Yes: 8 known advisories
Yes. github.com/modelcontextprotocol/registry 0.0.3, the last 0.0 release, is affected by 8 known security advisories (2 medium, 6 low), including CVE-2026-44430, CVE-2026-44429, CVE-2026-44429. Upgrade to 1.7.9 or later to fix all of them.
go get github.com/modelcontextprotocol/registry@v1.7.9Is your project on an affected github.com/modelcontextprotocol/registry?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/modelcontextprotocol/registry 0.0.3
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
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
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
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
MCP Registry: OCI validator skips ownership check on upstream rate limits
- Affected
- <1.7.9
- Fixed in
- 1.7.9
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
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
MCP Registry's GitHub OIDC tokens are replayable across registry deployments due to shared audience
- Affected
- <1.7.6
- Fixed in
- 1.7.6
Every github.com/modelcontextprotocol/registry 0.0.x release
Affected: 0.0.1 to 0.0.3. Latest github.com/modelcontextprotocol/registry: 1.8.9.
| Version | Known advisories |
|---|---|
| github.com/modelcontextprotocol/registry 0.0.3 | CVE-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 0.0.2 | CVE-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 0.0.1 | CVE-2026-44429, CVE-2026-44430, CVE-2026-44428, CVE-2026-45781, CVE-2026-45781, CVE-2026-44430, CVE-2026-44429, CVE-2026-44428 |
Which of your client projects are still on github.com/modelcontextprotocol/registry 0.0?
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
- github.com/modelcontextprotocol/registry 1.2
- github.com/modelcontextprotocol/registry 1.1
- github.com/modelcontextprotocol/registry 1.0
- github.com/modelcontextprotocol/registry 1.8
- github.com/modelcontextprotocol/registry 1.7
- github.com/modelcontextprotocol/registry 1.6
- github.com/modelcontextprotocol/registry 1.5
- github.com/modelcontextprotocol/registry 1.4
- github.com/modelcontextprotocol/registry 1.3
- All github.com/modelcontextprotocol/registry advisories
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.