MCP Registry's GitHub OIDC tokens are replayable across registry deployments due to shared audience
CVE-2026-44428 · GHSA-95c3-6vvw-4mrq · published 2026-05-08 · updated 2026-06-01
- Severity
- Low
- CVSS score
- 4.7
- Chance of exploitation (EPSS)
- 0.22%
- Fixed in
- 1.7.6
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
An attacker-controlled or compromised registry deployment can mint a valid registry JWT on another deployment and inherit publish permissions for the victim GitHub owner namespace. In practical terms, this enables unauthorized publication or update actions for names such as io.github. /* on the victim registry instance.
Upgrade github.com/modelcontextprotocol/registry to 1.7.6 or later.
1. Replace the shared audience string with a registry-specific audience, such as a deployment-specific client ID or origin-derived identifier. 2. Ensure the publisher requests the audience that matches the exact registry instance it is targeting, and ensure the server validates that same instance-specific value. 3. Consider binding the exchange to additional deployment-specific claims so that a token captured by one registry cannot be replayed on another. 4. Add regression tests that cover cross-deployment replay attempts between different registry URLs.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| github.com/modelcontextprotocol/registry | Go | < 1.7.6 | 1.7.6 |
- CriticalMLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebindingmlflowExploited
- Critical@zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery@zereight/mcp-gitlab
- CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
- CriticalLocalAI POST /models/apply permits unauthenticated server-side request forgery through gallery URLsgithub.com/mudler/LocalAI
- CriticalFastMCP OpenAPI Provider has an SSRF & Path Traversal Vulnerabilityfastmcp
- CriticalBentoML SSRF Vulnerability in File Upload Processingbentoml
- MediumMCP Registry has an unauthenticated SSRF: HTTP namespace verification dials 6to4 / NAT64 / site-local IPv6 addresses, bypassing private-addrgithub.com/modelcontextprotocol/registry
- MediumMCP Registry vulnerable to stored XSS in catalogue UI via attribute-quote breakout in publisher-controlled `websiteUrl`github.com/modelcontextprotocol/registry
- MediumMCP Registry has open redirect via protocol-relative path in trailing-slash middlewaregithub.com/modelcontextprotocol/registry
- LowMCP Registry: OCI validator skips ownership check on upstream rate limitsgithub.com/modelcontextprotocol/registry
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.