Project Subscriptions
No data.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-95c3-6vvw-4mrq | MCP Registry's GitHub OIDC tokens are replayable across registry deployments due to shared audience |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 15 May 2026 17:30:00 +0000
| 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
|
Fri, 15 May 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 14 May 2026 21:45:00 +0000
| 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
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-15T14:22:18.973Z
Reserved: 2026-05-06T14:40:00.953Z
Link: CVE-2026-44428
Updated: 2026-05-15T14:22:14.790Z
Status : Analyzed
Published: 2026-05-14T22:16:44.593
Modified: 2026-05-15T17:23:35.580
Link: CVE-2026-44428
No data.
OpenCVE Enrichment
Updated: 2026-05-14T22:30:25Z
Github GHSA