CVE-2026-52869

HIGHPre-NVD 7.17.1
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: cna:github_m
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: CVSS: 7.1Exploit: NoneExposed: 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.27.2, the SSE and stateful Streamable HTTP transports mcp.server.sse.SseServerTransport and mcp.server.streamable_http_manager.StreamableHTTPSessionManager route requests to existing sessions using only the session_id query parameter or Mcp-Session-Id header without verifying the authenticated principal that created the session, allowing a different bearer-token-authenticated client with a known session ID to inject JSON-RPC messages into that session. This issue is fixed in version 1.27.2.

CVSS v3
7.1
EG Score
7.1(low)
EPSS
KEV
Not listed

Published

July 15, 2026

Last Modified

July 15, 2026

Advisory Details (6)

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

HTTP transports serve session requests without verifying the authenticated principal · Advisory · modelcontextprotocol/python-sdk · GitHub

https://github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-jpw9-pfvf-9f58
github_release Patch Available

v1.27.2

Patch available: modelcontextprotocol/python-sdk v1.27.2

https://github.com/modelcontextprotocol/python-sdk/releases/tag/v1.27.2
github_pr Patch Available

[v1.x] Bind transport sessions to the authenticated principal

Patch available: modelcontextprotocol/python-sdk v1.27.2 (PR #2719 merged 2026-05-29)

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

[v1.x] Add subject and claims to AccessToken

Patch available: modelcontextprotocol/python-sdk v1.27.2 (PR #2690 merged 2026-05-26)

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

commit ce267b6fc515 (modelcontextprotocol/python-sdk)

Patch available: modelcontextprotocol/python-sdk v1.27.2 (contains commit ce267b6fc515)

https://github.com/modelcontextprotocol/python-sdk/commit/ce267b6fc515dc4efc1dc70b6975b16ff0feef0a
github_commit Patch Available

commit 1abcca2408a6 (modelcontextprotocol/python-sdk)

Patch available: modelcontextprotocol/python-sdk v1.27.2 (contains commit 1abcca2408a6)

https://github.com/modelcontextprotocol/python-sdk/commit/1abcca2408a6b50e10ec601181f63f9978705c00

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 2× in last 7d / 2× 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-15 20:10 UTCEG score recompute
  2. 2026-07-15 20:09 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-52869?
CVE-2026-52869 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.27.2, the SSE and stateful Streamable HTTP transports mcp.server.sse.SseServerTransport and mcp.server.streamablehttpmanager.StreamableHTTPSessionManager route requests to existing…
When was CVE-2026-52869 disclosed?
CVE-2026-52869 was first published in the National Vulnerability Database on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-52869?
CVE-2026-52869 has a CVSS v3 base score of 7.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-52869?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52869, 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-52869

Explore →

Is Your Infrastructure Affected by CVE-2026-52869?

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