MCP Registry: GitHub OIDC tokens replayable across registry deployments due to shared audience
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| modelcontextprotocol | registry | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Modelcontextprotocol | Registry |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-95c3-6vvw-4mrq | MCP Registry's GitHub OIDC tokens are replayable across registry deployments due to shared audience |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.219% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Modelcontextprotocol
Modelcontextprotocol registry |
|
| Vendors & Products |
Modelcontextprotocol
Modelcontextprotocol registry |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Lfprojects
Lfprojects mcp Registry |
|
| CPEs | cpe:2.3:a:lfprojects:mcp_registry:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Lfprojects
Lfprojects mcp Registry |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | MCP Registry: GitHub OIDC tokens replayable across registry deployments due to shared audience | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV4_0
|