2.1Düşük

CVE-2026-44428MCP Registry: GitHub OIDC tokens replayable across registry deployments due to shared audience

modelcontextprotocol registry Yayım: (5 ay önce)

Açıklama

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.

Zayıflık türü (CWE): CWE-918

Veri: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Bilgiler kaynaktaki haliyle, İngilizce yayımlanır.

Etkilenen ürünler ve sürümler

ÜreticiÜrünSürümler
lfprojects mcp registry < 1.7.6
modelcontextprotocol registry < 1.7.6

Kaynaklar ve yamalar

CPE eşleşmeleri (NVD) (1)

  • cpe:2.3:a:lfprojects:mcp_registry:*:*:*:*:*:*:*:* < 1.7.6