Skip to content

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

LowCVSS 2.1 EPSS 0.22%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial

Description

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.

Upgrade path

3 packages: 2 fixed.

PackageAffectedFixed inStatus
lfprojects mcp registry < 1.7.6 1.7.6 Fixed
modelcontextprotocol registry(Go) < 1.7.6 1.7.6 Fixed
modelcontextprotocol registry = < 1.7.6 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
modelcontextprotocol registry(Go) < 1.7.6 1.7.6
modelcontextprotocol registry = < 1.7.6 No fix listed
lfprojects mcp registry < 1.7.6 1.7.6

References