CVE-2026-11624

CRITICALPre-NVD 9.49.4—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% 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, secondary
Trending — 3 sources updated this week
9.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.4Exploit: NoneExposed: 0

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

The Model Context Protocol has a security warning advising servers to validate the "Origin" header on all incoming connections to prevent DNS rebinding attacks. Prior to the v0.25.0 release, users had no way to validate the origin's host. In v0.25.0, a new "--allowed-hosts" flag was introduced alongside the existing "--allowed-origins" flag, enabling users to specify permitted hosts at server startup. Both flags default to "*", allowing users to implement strict access controls as needed without breaking existing setups. If either flag is set to "*", the server will output a startup warning about potential vulnerabilities. Documentation has also been updated to highlight these security considerations.

CVSS v3
9.4
EG Score
9.4(medium)
EPSS
4.8%
KEV
Not listed

Published

June 13, 2026

Last Modified

June 16, 2026

Advisory Details (2)

Auto-updated Jun 13, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr.
github_pr Patch Available

feat: add allowed-hosts flag

Patch available: googleapis/mcp-toolbox v0.25.0 (PR #2254 merged 2026-01-08)

https://github.com/googleapis/mcp-toolbox/pull/2254
generic🟡 PoC Available

Default DNS-rebinding protection allows all domains by defaults · Issue #3113 · googleapis/mcp-toolbox · GitHub

https://github.com/googleapis/mcp-toolbox/issues/3113

Vendor Advisories for CVE-2026-11624(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 70× in last 7d / 272× 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.

Showing the most recent 100 of 272 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-11624?
CVE-2026-11624 is a critical vulnerability published on June 13, 2026. The Model Context Protocol has a security warning advising servers to validate the "Origin" header on all incoming connections to prevent DNS rebinding attacks. Prior to the v0.25.0 release, users had no way to validate the origin's host. In v0.25.0, a new "--allowed-hosts" flag was introduced…
When was CVE-2026-11624 disclosed?
CVE-2026-11624 was first published in the National Vulnerability Database on June 13, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11624 actively exploited?
CVE-2026-11624 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-11624?
CVE-2026-11624 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-11624?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11624, 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

Explore the affected products and dependency analysis for CVE-2026-11624

Explore →

Is Your Infrastructure Affected by CVE-2026-11624?

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

Start Free Scan →Browse All CVEs