CVE-2026-44429

MEDIUMNVD 5.45.4
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
5.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 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 v3
5.4
EG Score
5.4(medium)
EPSS
6.3%
KEV
Not listed

Published

May 14, 2026

Last Modified

May 15, 2026

Advisory Details (1)

Auto-updated Jun 17, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Stored XSS in catalogue UI via attribute-quote breakout in publisher-controlled `websiteUrl` · Advisory · modelcontextprotocol/registry · GitHub

https://github.com/modelcontextprotocol/registry/security/advisories/GHSA-rqv2-m695-f8j4

Vendor Advisories for CVE-2026-44429(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/modelcontextprotocol/registry1.7.7

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 42× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:16 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-29 21:40 UTCEG score recompute
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-27 23:18 UTCEG score recompute
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-26 21:08 UTCEG score recompute
  18. 2026-06-25 18:59 UTCEG score recompute
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 14:05 UTCEPSS rescore
  22. 2026-06-23 21:33 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
Show 62 more
  1. 2026-06-21 14:56 UTCEPSS rescore
  2. 2026-06-21 01:59 UTCEPSS rescore
  3. 2026-06-19 19:25 UTCEPSS rescore
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-18 17:52 UTCEPSS rescore
  6. 2026-06-18 04:25 UTCEG score recompute
  7. 2026-06-17 17:53 UTCEPSS rescore
  8. 2026-06-17 01:52 UTCEG score recompute
  9. 2026-06-16 17:52 UTCEPSS rescore
  10. 2026-06-15 23:43 UTCEG score recompute
  11. 2026-06-15 17:49 UTCEPSS rescore
  12. 2026-06-14 07:32 UTCEG score recompute
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-13 05:23 UTCEG score recompute
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-06-12 23:12 UTCEPSS rescore
  17. 2026-06-12 03:11 UTCEG score recompute
  18. 2026-06-11 14:00 UTCEPSS rescore
  19. 2026-06-11 01:02 UTCEG score recompute
  20. 2026-06-10 22:18 UTCEPSS rescore
  21. 2026-06-10 13:22 UTCEPSS rescore
  22. 2026-06-10 13:22 UTCEPSS rescore
  23. 2026-06-09 22:53 UTCEG score recompute
  24. 2026-06-08 20:44 UTCEG score recompute
  25. 2026-06-08 14:17 UTCEPSS rescore
  26. 2026-06-08 14:17 UTCEPSS rescore
  27. 2026-06-07 18:35 UTCEG score recompute
  28. 2026-06-07 15:25 UTCEPSS rescore
  29. 2026-06-07 15:25 UTCEPSS rescore
  30. 2026-06-06 16:24 UTCEG score recompute
  31. 2026-06-06 13:47 UTCEPSS rescore
  32. 2026-06-06 13:47 UTCEPSS rescore
  33. 2026-06-05 22:47 UTCEPSS rescore
  34. 2026-06-05 14:15 UTCEG score recompute
  35. 2026-06-05 06:10 UTCEPSS rescore
  36. 2026-06-05 06:10 UTCEPSS rescore
  37. 2026-06-04 13:12 UTCEPSS rescore
  38. 2026-06-04 13:12 UTCEPSS rescore
  39. 2026-06-04 12:06 UTCEG score recompute
  40. 2026-06-03 09:57 UTCEG score recompute
  41. 2026-06-02 20:13 UTCEPSS rescore
  42. 2026-06-02 07:48 UTCEG score recompute
  43. 2026-06-01 13:52 UTCEPSS rescore
  44. 2026-06-01 13:52 UTCEPSS rescore
  45. 2026-06-01 05:39 UTCEG score recompute
  46. 2026-05-31 22:30 UTCEPSS rescore
  47. 2026-05-31 22:30 UTCEPSS rescore
  48. 2026-05-31 00:16 UTCEPSS rescore
  49. 2026-05-31 00:16 UTCEPSS rescore
  50. 2026-05-29 13:44 UTCEPSS rescore
  51. 2026-05-29 13:44 UTCEPSS rescore
  52. 2026-05-28 13:44 UTCEPSS rescore
  53. 2026-05-28 13:44 UTCEPSS rescore
  54. 2026-05-27 13:40 UTCEPSS rescore
  55. 2026-05-27 13:40 UTCEPSS rescore
  56. 2026-05-26 13:44 UTCEPSS rescore
  57. 2026-05-26 07:18 UTCEPSS rescore
  58. 2026-05-23 00:07 UTCEG score recompute
  59. 2026-05-21 22:43 UTCEPSS rescore
  60. 2026-05-20 22:38 UTCEPSS rescore
  61. 2026-05-20 12:08 UTCEG score recompute
  62. 2026-05-20 11:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-44429?
CVE-2026-44429 is a medium vulnerability published on May 14, 2026. 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…
When was CVE-2026-44429 disclosed?
CVE-2026-44429 was first published in the National Vulnerability Database on May 14, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44429 actively exploited?
CVE-2026-44429 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44429?
CVE-2026-44429 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-44429?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44429, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44429

Explore →

Is Your Infrastructure Affected by CVE-2026-44429?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.