4.7

CVE-2026-44428: lfprojects mcp_registry Server-Side Request Forgery (SSRF)

CVSS: 4.7v3.1MediumAnalyzed
AliasesCGA-7gx7-h89w-mjvwCGA-rr75-23qc-m4v3GHSA-95c3-6vvw-4mrq
Published 14-05-2026Last modified 15-05-2026

Vulnerability summary

CVE-2026-44428 is a medium (CVSS 4.7) Server-Side Request Forgery (SSRF) vulnerability in lfprojects mcp_registry. EPSS estimates a 0.27% chance of exploitation in the next 30 days, higher than 17.2% of scored vulnerabilities.

Overall risk
19/100
0100
Low · default modelHow is this calculated?
CVSS score
4.7/10
010
Medium · v3.1 (NVD)
EPSS score
0.27%
0%100%
Low · +0.05 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 1 · Related 2

Timeline

  1. 14-05-2026
    PublishedVulnerability first disclosed.
  2. 15-05-2026
    Last modifiedVulnerability information updated.

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 metrics

7 scores · 5 sources · 2 versions

EPSS trend

Probability

0.27%

Chance of exploitation in the next 30 days

Percentile

17%

Versus all other CVEs

30-day change

+0.05 pp

From 0.22% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.27%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Chainguard1 product
  • goreleaser< 2.15.4-r2 | < 2.15.4-r1
Github.com/modelcontextprotocol1 product
  • registry< 1.7.6
Lfprojects1 product
Modelcontextprotocol1 product
Wolfi1 product
  • goreleaser< 2.15.4-r2 | < 2.15.4-r1

5 vendors · 5 products

References

7 links