CVE-2026-50287

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 72% 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
Elevated
8.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.7Exploit: NoneExposed: 0

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

AgenticMail gives AI agents real email addresses and phone numbers. Prior to version 0.9.27, @agenticmail/mcp exposes a Streamable HTTP transport when started with --http or MCP_HTTP=1. In that mode, the /mcp endpoint accepts requests without any HTTP authentication layer. A remote client can initialize a session and call tools directly. This issue has been patched in version 0.9.27.

CVSS v3
8.7
EG Score
8.7(medium)
EPSS
27.9%
KEV
Not listed

Published

June 1, 2026

Last Modified

June 16, 2026

Advisory Details (1)

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

Missing Authentication for Critical Function in @agenticmail/mcp · Advisory · agenticmail/agenticmail · GitHub

https://github.com/agenticmail/agenticmail/security/advisories/GHSA-63gr-g7jc-v8rg

Vendor Advisories for CVE-2026-50287(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)
npm(1)
PackageVulnerable rangeFixed inDependents
@agenticmail/mcp0.9.27

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-50287?
CVE-2026-50287 is a high vulnerability published on June 1, 2026. AgenticMail gives AI agents real email addresses and phone numbers. Prior to version 0.9.27, @agenticmail/mcp exposes a Streamable HTTP transport when started with --http or MCP_HTTP=1. In that mode, the /mcp endpoint accepts requests without any HTTP authentication layer. A remote client can…
When was CVE-2026-50287 disclosed?
CVE-2026-50287 was first published in the National Vulnerability Database on June 1, 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-50287 actively exploited?
CVE-2026-50287 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50287?
CVE-2026-50287 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-50287?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50287, 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-50287

Explore →

Is Your Infrastructure Affected by CVE-2026-50287?

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