5.4

CVE-2026-44429: lfprojects mcp_registry Cross-site Scripting

CVSS: 5.4v3.1MediumAnalyzed
AliasesCGA-ggq7-7f6f-7cvgCGA-xx2p-jg37-gv3wGHSA-rqv2-m695-f8j4
Published 14-05-2026Last modified 15-05-2026

Vulnerability summary

CVE-2026-44429 is a medium (CVSS 5.4) Cross-site Scripting vulnerability in lfprojects mcp_registry. EPSS estimates a 0.24% chance of exploitation in the next 30 days, higher than 13.9% of scored vulnerabilities. 1 public exploit is recorded.

Overall risk
32/100
0100
Medium · default modelHow is this calculated?
CVSS score
5.4/10
010
Medium · v3.1 (NVD)
EPSS score
0.24%
0%100%
Low · +0.07 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits1github

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.7, the public catalogue UI served at GET / (file internal/api/handlers/v0/ui_index.html) is vulnerable to stored cross-site scripting via the server.websiteUrl field of any published server.json. Server-side validation in internal/validators/validators.go (validateWebsiteURL) only checks that the URL parses, is absolute, and uses the https scheme; it does not reject quote characters. Client-side, the value is interpolated into a double-quoted href attribute via innerHTML, using a homegrown escapeHtml helper that performs the standard textContent → innerHTML round-trip. Per the HTML serialisation algorithm, that round-trip encodes only &, <, > and U+00A0 inside text nodes — it does not encode " or '. A literal " in websiteUrl therefore breaks out of the href attribute, allowing arbitrary on* event handlers to be appended to the same <a> element. The Content-Security-Policy on / is script-src 'self' 'unsafe-inline' https://cdn.tailwindcss.com, so the injected event handlers execute. Any user able to obtain a publish token (e.g. via POST /v0/auth/github-at with their own GitHub account, or POST /v0/auth/none on a deployment that has anonymous auth enabled) can plant a poisoned record visible to every visitor of the registry homepage. This vulnerability is fixed in 1.7.7.

CVSS metrics

7 scores · 5 sources · 2 versions

EPSS trend

Probability

0.24%

Chance of exploitation in the next 30 days

Percentile

14%

Versus all other CVEs

30-day change

+0.07 pp

From 0.17% on 19-09-2026

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

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

1 found
  • githubUnverified

    Registry

    Maturity: poc

Weaknesses

CWE · root cause

Affected systems

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

5 vendors · 5 products

References

7 links