Skip to main content
VulnerabilityPublished Updated

CVE-2026-52869: MCP Python SDK · HTTP transports serve session requests without verifying the authenticated principal

Affects mistral-vibeSource GCVE Database

0
Compare
Authoritative record:CVE-2026-52869· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 2.17.0 soon.

Data as of 30 Oct 2026, 08:03 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
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:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Homebrewmistral-vibepkg:brew/mistral-vibeOther threatsAffected
  • >=1.1.1 <2.17.0
Fixed in
  • 2.17.0

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

Community reviews

Loading reviews…