Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Lfprojects | Mcp Registry | < 1.7.6 |
Related Weaknesses (CWE)
References
- https://github.com/modelcontextprotocol/registry/security/advisories/GHSA-95c3-6MitigationVendor Advisory
FAQ
What is CVE-2026-44428?
CVE-2026-44428 is a vulnerability with a CVSS score of 4.7 (MEDIUM). 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...
How severe is CVE-2026-44428?
CVE-2026-44428 has been rated MEDIUM with a CVSS base score of 4.7/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-44428?
Check the references section above for vendor advisories and patch information. Affected products include: Lfprojects Mcp Registry.