Vulnerability Details CVE-2026-44429
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.
Exploit prediction scoring system (EPSS) score
EPSS Score 0.0
EPSS Ranking 10.8%
CVSS Severity
CVSS v3 Score 5.4
Products affected by CVE-2026-44429
-
cpe:2.3:a:lfprojects:mcp_registry:0.0.1
-
cpe:2.3:a:lfprojects:mcp_registry:0.0.2
-
cpe:2.3:a:lfprojects:mcp_registry:0.0.3
-
cpe:2.3:a:lfprojects:mcp_registry:1.0.0
-
cpe:2.3:a:lfprojects:mcp_registry:1.1.0
-
cpe:2.3:a:lfprojects:mcp_registry:1.2.0
-
cpe:2.3:a:lfprojects:mcp_registry:1.2.1
-
cpe:2.3:a:lfprojects:mcp_registry:1.2.2
-
cpe:2.3:a:lfprojects:mcp_registry:1.2.3
-
cpe:2.3:a:lfprojects:mcp_registry:1.3.0
-
cpe:2.3:a:lfprojects:mcp_registry:1.3.1
-
cpe:2.3:a:lfprojects:mcp_registry:1.3.10
-
cpe:2.3:a:lfprojects:mcp_registry:1.3.2
-
cpe:2.3:a:lfprojects:mcp_registry:1.3.3
-
cpe:2.3:a:lfprojects:mcp_registry:1.3.4
-
cpe:2.3:a:lfprojects:mcp_registry:1.3.5
-
cpe:2.3:a:lfprojects:mcp_registry:1.3.6
-
cpe:2.3:a:lfprojects:mcp_registry:1.3.7
-
cpe:2.3:a:lfprojects:mcp_registry:1.3.8
-
cpe:2.3:a:lfprojects:mcp_registry:1.3.9
-
cpe:2.3:a:lfprojects:mcp_registry:1.4.0
-
cpe:2.3:a:lfprojects:mcp_registry:1.4.1
-
cpe:2.3:a:lfprojects:mcp_registry:1.5.0
-
cpe:2.3:a:lfprojects:mcp_registry:1.6.0
-
cpe:2.3:a:lfprojects:mcp_registry:1.7.0
-
cpe:2.3:a:lfprojects:mcp_registry:1.7.1
-
cpe:2.3:a:lfprojects:mcp_registry:1.7.2
-
cpe:2.3:a:lfprojects:mcp_registry:1.7.3
-
cpe:2.3:a:lfprojects:mcp_registry:1.7.4
-
cpe:2.3:a:lfprojects:mcp_registry:1.7.5
-
cpe:2.3:a:lfprojects:mcp_registry:1.7.6