CVE-2026-52869: MCP Python SDK · HTTP transports serve session requests without verifying the authenticated principal
Affects mistral-vibeSource GCVE Database
Not known to be exploited · CVSS 7.1 High : upgrade to 2.17.0 soon.
Data as of 30 Oct 2026, 08:03 UTC
- Patch
- Available – fixed in 2.17.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 15 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade mistral-vibe to 2.17.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewmistral-vibepkg:brew/mistral-vibeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade affected MCP Python SDK versions to 2.17.0 or later, which implements verification of the authenticated principal against the session creator and rejects requests with mismatched principals. Deployments where many users share a single OAuth client should ensure the token verifier populates the AccessToken.subject claim to isolate sessions per user. Custom authentication backends must implement equivalent principal verification to prevent session hijacking.
Description
A vulnerability in the MCP Python SDK HTTP transports (SSE and Streamable HTTP in stateful mode) allows session hijacking by bypassing authentication checks. Incoming requests are routed to existing sessions based solely on session IDs without verifying the authenticated principal. This enables an attacker who obtains a session ID to send JSON-RPC messages on that session regardless of the bearer token used. The issue affects versions from 1.1.1 up to but not including 2.17.0. A fix is available in version 2.17.0.
References
- github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-jpw9-pfvf-9f58 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-52869 (opens in a new tab)
- github.com/modelcontextprotocol/python-sdk/pull/2690 (opens in a new tab)
- github.com/modelcontextprotocol/python-sdk/pull/2719 (opens in a new tab)
- github.com/modelcontextprotocol/python-sdk/commit/1abcca2408a6b50e10ec601181f63f9978705c00 (opens in a new tab)
- github.com/modelcontextprotocol/python-sdk/commit/ce267b6fc515dc4efc1dc70b6975b16ff0feef0a (opens in a new tab)
- github.com/modelcontextprotocol/python-sdk (opens in a new tab)
- github.com/modelcontextprotocol/python-sdk/releases/tag/v1.27.2 (opens in a new tab)