Read the docs
TI-2026-32369 Aliases CVE-2026-44428GHSA-95c3-6vvw-4mrq

MCP Registry: GitHub OIDC tokens replayable across registry deployments due to shared audience

Priority LOW 11CWE-918Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Active
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00219 12th percentileScored 2026-11-07
Fix Fixed registry (modelcontextprotocol): 1.7.6github.com/modelcontextprotocol/registry (Go): 1.7.6

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
MLflowregistrybefore 1.7.61.7.6Patch availableCNA
—github.com/modelcontextprotocol/registry (Go)before 1.7.61.7.6Patch availableGHSA-95c3-6vvw-4mrq
  • registry VendorMLflow Affected before 1.7.6 Fixed in 1.7.6 Patch available CNA
  • github.com/modelcontextprotocol/registry (Go) Vendor— Affected before 1.7.6 Fixed in 1.7.6 Patch available GHSA-95c3-6vvw-4mrq

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:lfprojects:mcp_registry:*:*:*:*:*:*:*:*before 1.7.6VulnerableMLflow
  • cpe:2.3:a:lfprojects:mcp_registry:*:*:*:*:*:*:*:* Versions before 1.7.6 Vulnerable ·MLflow

Remediation

  • Fix · CNA registry (modelcontextprotocol) Fixed in 1.7.6
  • Fix · GHSA-95c3-6vvw-4mrq github.com/modelcontextprotocol/registry (Go) Fixed in 1.7.6 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-44428
  2. 2026-10-03 Alias added: GHSA-95c3-6vvw-4mrq

References

Advisory 2

Other 4

  • TI-2026-32371 Server-side request forgery in MLflow registry CVSS 4.0MEDIUM 6.3
  • TI-2026-32370 MCP Registry: Stored XSS in catalogue UI via attribute-quote breakout in publisher-controlled `websiteUrl` CVSS 4.0MEDIUM 5.1

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences