UTC
High

MCP Python SDK: HTTP transports serve session requests without verifying the authenticated principal

CVE-2026-52869 · GHSA-jpw9-pfvf-9f58 · published 2026-07-16

Severity
High
CVSS score
7.1
Chance of exploitation (EPSS)
0.53%
Fixed in
1.27.2
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Total
  • CISA SSVC
What it is

Servers using either HTTP transport together with the SDK's built-in bearer-token authentication are affected: the per-client isolation that authentication provides can be bypassed for any session whose ID is known. Session IDs are randomly generated UUIDs, so exploitation requires obtaining one out of band (logs, network observation). Servers that do not enable bearer-token authentication have no per-client isolation to bypass and are not addressed by this advisory, and stateless Streamable HTTP deployments do not maintain sessions and are unaffected.

What to do

Upgrade mcp to 1.27.2 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

If you cannot upgrade yet

Upgrade to version 1.27.2 or later, which records the authenticated principal that created each session — the OAuth client ID together with the token's issuer and subject when the token verifier supplies them — and answers requests presenting a different principal with the same 404 response as for an unknown session. Deployments where many end users share a single OAuth client (hosted MCP clients, gateways) should ensure their token verifier populates AccessToken.subject (e.g. from the token's sub claim) so sessions are isolated per user rather than per client.

Affected
PackageRegistryAffectedFixed in
mcpPyPI<= 1.27.11.27.2
Downstream in the Official MCP Registry

17 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.

  • com.cyberspf/mcpmcp@1.9.4
  • io.github.abhichandra21/promptheusmcp@1.12.4
  • io.github.AdonaiVera/fiftyone-mcp-servermcp@0.9.1
  • io.github.AndreySukhanov/summarix-telegrammcp@1.12.4
  • io.github.ashlesh-t/cognirepomcp@1.27.0
  • io.github.cr7258/elasticsearch-mcp-servermcp@1.9.2
  • io.github.domdomegg/time-mcp-pypimcp@1.13.1
  • io.github.gokeshenzhen/traceweavemcp@1.27.0
  • io.github.klein-business/legal-text-mcp-demcp@1.27.1
  • io.github.kushknows/weather-mcp-servermcp@1.13.1
  • io.github.luarss/openroad-mcpmcp@1.26.0
  • io.github.oraios/serenamcp@1.27.0
All 17 servers on the trace →

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].