Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CVE-2026-44428— MCP Registry: GitHub OIDC tokens replayable across registry deployments due to shared audience

AI Predicted 9.8 Difficulty: Easy EPSS 0.03% · P11

Possible ATT&CK Techniques 1AI

T1078 · Valid Accounts

Affected Version Matrix 1

VendorProductVersion RangeStatus
modelcontextprotocolregistry< 1.7.6affected
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-44428

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
MCP Registry: GitHub OIDC tokens replayable across registry deployments due to shared audience
Source: NVD (National Vulnerability Database)
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.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
服务端请求伪造(SSRF)
Source: NVD (National Vulnerability Database)
Vulnerability Title
MCP Registry 代码问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
MCP Registry是Model Context Protocol开源的一个MCP服务器应用商店。 MCP Registry 1.7.6之前版本存在代码问题漏洞，该漏洞源于客户端和服务器端GitHub OIDC流程仅绑定到全局受众字符串而非特定注册表实例，导致从一个注册表部署合法获取的令牌可被其他共享相同代码和受众字符串的部署接受。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
modelcontextprotocolregistry < 1.7.6 -

II. Public POCs for CVE-2026-44428

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-44428

请登录查看更多情报信息。

Same Patch Batch · modelcontextprotocol · 2026-05-14 · 6 CVEs total

CVE-2026-425598.8 HIGHRMCP: DNS rebinding vulnerability in rmcp Streamable HTTP server transport
CVE-2026-457813.5 LOWMCP Registry: OCI ownership validation fails open on upstream rate limits, allowing attack
CVE-2026-44429MCP Registry: Stored XSS in catalogue UI via attribute-quote breakout in publisher-control
CVE-2026-44430MCP Registry: Unauthenticated SSRF: HTTP namespace verification dials 6to4 / NAT64 / site-
CVE-2026-44427MCP Registry: Open Redirect

IV. Related Vulnerabilities

Same product: registry
Same vendor: modelcontextprotocol
Same weakness: CWE-918

V. Comments for CVE-2026-44428

No comments yet

Leave a comment