CVE-2026-59950

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 86% 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
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

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

The MCP Python SDK, called mcp on PyPI, is a Python implementation of the Model Context Protocol (MCP). Prior to 1.28.1, the deprecated mcp.server.websocket.websocket_server transport accepted WebSocket handshakes without applying Host or Origin header validation, leaving no SDK-level way to restrict which origins could connect to applications that exposed that transport. This issue is fixed in version 1.28.1.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

July 15, 2026

Last Modified

July 17, 2026

Advisory Details (4)

Auto-updated Jul 15, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v1.28.1

Patch available: modelcontextprotocol/python-sdk v1.28.1

https://github.com/modelcontextprotocol/python-sdk/releases/tag/v1.28.1
github_commit

commit 777b8d06710c (modelcontextprotocol/python-sdk)

Fix landed in modelcontextprotocol/python-sdk commit 777b8d06710c — awaiting tagged release

https://github.com/modelcontextprotocol/python-sdk/commit/777b8d06710c140e3606b0d4598e2aa48546c266
github_pr

[v1.x] Support TransportSecuritySettings in the WebSocket server transport

Fix merged in modelcontextprotocol/python-sdk PR #2992 on 2026-06-26 — awaiting tagged release

https://github.com/modelcontextprotocol/python-sdk/pull/2992
github Patch Available

WebSocket server transport does not support Host/Origin validation · Advisory · modelcontextprotocol/python-sdk · GitHub

https://github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-vj7q-gjh5-988w

Vendor Advisories for CVE-2026-59950(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)
PyPI(1)
PackageVulnerable rangeFixed inDependents
mcp0.9.1 ... 1.9.4 (57 versions)1.28.1—

Weakness Classification(2)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-59950?
CVE-2026-59950 is a high vulnerability published on July 15, 2026. The MCP Python SDK, called mcp on PyPI, is a Python implementation of the Model Context Protocol (MCP). Prior to 1.28.1, the deprecated mcp.server.websocket.websocket_server transport accepted WebSocket handshakes without applying Host or Origin header validation, leaving no SDK-level way to…
When was CVE-2026-59950 disclosed?
CVE-2026-59950 was first published in the National Vulnerability Database on July 15, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59950 actively exploited?
CVE-2026-59950 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.3% of all scored CVEs.
What is the CVSS score of CVE-2026-59950?
CVE-2026-59950 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-59950?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59950, 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-59950

Explore →

Is Your Infrastructure Affected by CVE-2026-59950?

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

Start Free Scan →Browse All CVEs