CVE-2026-44427

NONENVD 0.0Elevated
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: —Exploit: 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. From 1.1.0 to 1.7.4, the TrailingSlashMiddleware in internal/api/server.go is vulnerable to an open redirect attack. An attacker can craft a URL with a protocol-relative path (e.g., //evil.com/) that, after trailing slash removal, results in a Location header of //evil.com — which browsers interpret as an absolute URL to an external domain. This vulnerability is fixed in 1.7.5.

CVSS v3
—
EG Score
0.0(none)
EPSS
32.9%
KEV
Not listed

Published

May 14, 2026

Last Modified

May 15, 2026

References (2)

Vendor Advisories for CVE-2026-44427(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/registry—1.7.5—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-27 03:08 UTCEPSS rescore
  15. 2026-06-25 13:49 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-24 14:05 UTCEPSS rescore
  18. 2026-06-23 21:33 UTCEPSS rescore
  19. 2026-06-22 14:25 UTCEPSS rescore
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-21 14:56 UTCEPSS rescore
  22. 2026-06-21 14:56 UTCEPSS rescore
  23. 2026-06-21 01:59 UTCEPSS rescore
  24. 2026-06-19 19:25 UTCEPSS rescore
  25. 2026-06-18 17:52 UTCEPSS rescore
Show 39 more
  1. 2026-06-18 17:52 UTCEPSS rescore
  2. 2026-06-17 17:53 UTCEPSS rescore
  3. 2026-06-16 17:52 UTCEPSS rescore
  4. 2026-06-15 17:49 UTCEPSS rescore
  5. 2026-06-13 23:00 UTCEPSS rescore
  6. 2026-06-11 14:00 UTCEPSS rescore
  7. 2026-06-10 22:18 UTCEPSS rescore
  8. 2026-06-10 13:22 UTCEPSS rescore
  9. 2026-06-10 13:22 UTCEPSS rescore
  10. 2026-06-08 14:17 UTCEPSS rescore
  11. 2026-06-08 14:17 UTCEPSS rescore
  12. 2026-06-07 15:25 UTCEPSS rescore
  13. 2026-06-07 15:25 UTCEPSS rescore
  14. 2026-06-06 13:47 UTCEPSS rescore
  15. 2026-06-06 13:47 UTCEPSS rescore
  16. 2026-06-05 22:47 UTCEPSS rescore
  17. 2026-06-05 06:10 UTCEPSS rescore
  18. 2026-06-05 06:10 UTCEPSS rescore
  19. 2026-06-04 13:12 UTCEPSS rescore
  20. 2026-06-04 13:12 UTCEPSS rescore
  21. 2026-06-02 20:13 UTCEPSS rescore
  22. 2026-06-01 13:52 UTCEPSS rescore
  23. 2026-06-01 13:52 UTCEPSS rescore
  24. 2026-05-31 22:30 UTCEPSS rescore
  25. 2026-05-31 22:30 UTCEPSS rescore
  26. 2026-05-31 00:16 UTCEPSS rescore
  27. 2026-05-31 00:16 UTCEPSS rescore
  28. 2026-05-29 13:44 UTCEPSS rescore
  29. 2026-05-29 13:44 UTCEPSS rescore
  30. 2026-05-28 13:44 UTCEPSS rescore
  31. 2026-05-28 13:44 UTCEPSS rescore
  32. 2026-05-27 13:40 UTCEPSS rescore
  33. 2026-05-27 13:40 UTCEPSS rescore
  34. 2026-05-26 13:44 UTCEPSS rescore
  35. 2026-05-26 07:18 UTCEPSS rescore
  36. 2026-05-21 22:43 UTCEPSS rescore
  37. 2026-05-20 22:38 UTCEPSS rescore
  38. 2026-05-20 12:07 UTCEG score recompute
  39. 2026-05-20 11:22 UTCEPSS rescore

Frequently asked(4)

What is CVE-2026-44427?
CVE-2026-44427 is a none 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. From 1.1.0 to 1.7.4, the TrailingSlashMiddleware in internal/api/server.go is vulnerable to an open redirect attack. An attacker can craft a URL with a protocol-relative path (e.g., //evil.com/)…
When was CVE-2026-44427 disclosed?
CVE-2026-44427 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-44427 actively exploited?
CVE-2026-44427 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 32.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2026-44427?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44427, 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-44427

Explore →

Is Your Infrastructure Affected by CVE-2026-44427?

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

Start Free Scan →Browse All CVEs