CVE-2026-44428
The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
Auswirkung
The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers. Prior to 1.7.6, the client-side and server-side GitHub OIDC flow is bound only to a global audience string, not to the specific registry instance being targeted. On the client side, the publisher always appends audience=mcp-registry when requesting the GitHub Actions ID token, regardless of the selected --registry URL. On the server side, the exchange endpoint validates only that same fixed audience and then derives publish permissions directly from repository_owner. As a result, a token legitimately obtained while interacting with one registry deployment remains acceptable to any other deployment that shares the same code and audience string. This vulnerability is fixed in 1.7.6.
Ein Angreifer kann die Lücke über das Netzwerk ausnutzen, ohne Anmeldung, allerdings muss ein Nutzer etwas tun, etwa eine Datei oder einen Link öffnen. Bei Erfolg: geringes Risiko, dass Daten oder Systeme verändert werden. Der Angriff kann über die verwundbare Komponente hinaus wirken.
Betroffene Pakete
| Ökosystem | Paket | Betroffen | Behoben in |
|---|---|---|---|
| go | github.com/modelcontextprotocol/registry | < 1.7.6 | 1.7.6 |
Betroffene Produkte · Lfprojects
| Produkt | Betroffene Versionen |
|---|---|
| Mcp Registry | vor 1.7.6 |
Schwachstellenklasse
Referenzen
- NVD-Eintrag
- CVE.org-Eintrag
- GitHub-Advisory
- https://github.com/advisories/GHSA-95c3-6vvw-4mrq
- https://github.com/modelcontextprotocol/registry/security/advisories/GHSA-95c3-6vvw-4mrq
- https://github.com/modelcontextprotocol/registry/pull/1229
- https://github.com/modelcontextprotocol/registry/commit/3f89fc2b1fb34fd49f3c0e1b39e964a5c67b613f
- https://github.com/modelcontextprotocol/registry/releases/tag/v1.7.6
- https://nvd.nist.gov/vuln/detail/CVE-2026-44428