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.
go get github.com/modelcontextprotocol/registry@v1.8.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
Security advisories for github.com/modelcontextprotocol/registry
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 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
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
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?
- github.com/modelcontextprotocol/registry 1.8No known advisories in 1.8.9
- github.com/modelcontextprotocol/registry 1.7No known advisories in 1.7.9
- github.com/modelcontextprotocol/registry 1.610 advisories in 1.6.0
- github.com/modelcontextprotocol/registry 1.510 advisories in 1.5.0
- github.com/modelcontextprotocol/registry 1.410 advisories in 1.4.1
- github.com/modelcontextprotocol/registry 1.310 advisories in 1.3.10
- github.com/modelcontextprotocol/registry 0.08 advisories in 0.0.3
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.