Dashboard / CVE-2026-44428

CVE-2026-44428

LOW
INFO Priority: 0.00 BB Relevance: 54/100
Published: 2026-05-14 Modified: 2026-10-26 First seen: 2026-10-29 Status: active

Attack Surface

Network Low Complexity No Auth

CVSS Vector Breakdown

AV: Network
AC: Low
PR: None
UI: Active
S: X
AT: Present
VC: None
VI: Low
VA: None

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.

Weakness Classification (1)

Affected Software (1)

VendorProductVersion
lfprojects mcp_registry < 1.7.6

References & Advisories (1)

Bug Bounty Relevance

54 / 100
✓ Network accessible
✓ No authentication
✓ Low complexity

CVSS Score

2.1 / 10.0 v4.0
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

EPSS — Exploitation Probability

0.22%
Raw Score 0.002190
Percentile 12.4%
Date 2026-10-29

EPSS Trend

2026-10-29
0.00219
2026-10-28
0.00219

Intelligence Sources

nvd ref →

External Links