CVE-2026-44428
- Source
- https://cve.org/CVERecord?id=CVE-2026-44428
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-44428.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-44428
- Aliases
- Related
- Published
- 2026-05-14T21:09:10.092Z
- Modified
- 2026-07-08T08:13:28.169584516Z
- Severity
-
- 2.1 (Low) CVSS_V4 - 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 CVSS Calculator
- Summary
- MCP Registry: GitHub OIDC tokens replayable across registry deployments due to shared audience
- Details
-
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.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/44xxx/CVE-2026-44428.json", "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-918" ] }- References
Affected packages
Git / github.com/modelcontextprotocol/registry
Affected ranges
- Type
- GIT
- Repo
- https://github.com/modelcontextprotocol/registry
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixed
- Database specific
{ "cpe": "cpe:2.3:a:lfprojects:mcp_registry:*:*:*:*:*:*:*:*", "extracted_events": [ { "introduced": "0" }, { "fixed": "1.7.6" } ], "source": [ "AFFECTED_FIELD", "CPE_RANGE" ] }