{"id":"CVE-2026-44428","revision":"1bce0d47494e428fa70d2f70b8ee1cfd","records":[{"revision":"1bce0d47494e428fa70d2f70b8ee1cfd","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2026-44428","aliases":[],"title":"MCP Registry: GitHub OIDC tokens replayable across registry deployments due to shared audience","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.","state":0,"publishedAt":"2026-05-14T21:09:10.092+00:00","modifiedAt":"2026-05-15T14:22:18.973+00:00","affected":[{"ecosystem":"Vendor product","name":"registry","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"modelcontextprotocol\",\n                    \"product\": \"registry\",\n                    \"versions\": [\n                        {\n                            \"version\": \"< 1.7.6\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 4.0","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N","score":2.1,"severity":"LOW"}],"references":["https://github.com/modelcontextprotocol/registry/security/advisories/GHSA-95c3-6vvw-4mrq"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-44428","license":"CVE Program Terms of Use","key":"cve-program:CVE-2026-44428","identifiers":["CVE-2026-44428"]},"retained":false,"historicalAffected":[]}],"coverage":[]}