UTC
Medium

Model Context Protocol Python SDK: Server bearer-token authentication accepts tokens issued for a different resource server

CVE-2026-116684 · GHSA-w4fh-qvv9-3v23 · published 2026-10-27

Severity
Medium
CVSS score
6.8
Chance of exploitation (EPSS)
0.36%
Fixed in
2.2.0
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Total
  • CISA SSVC
What it is

In affected versions, the SDK's server-side bearer authentication had no way to check that a token was issued for your server (its audience). Where one authorization server issues tokens for several services, a valid token for another service was also accepted by your MCP server.

What to do

Upgrade mcp to 2.2.0 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.

Upgrade to: 1.x: mcp 1.30.0 or later 2.x: mcp 2.2.0 or later Upgrading alone changes nothing. The patched versions add a validatetokenresource setting that is off unless you set it. To turn the check on, make both of these changes together: 1. Set validatetokenresource=True in AuthSettings, with resourceserverurl set to the audience your authorization server puts in tokens for your server. 2. Return the token's audience from verifytoken() as AccessToken.resource. A token for another service then gets 401. With only the first change, every request gets 401. If your TokenVerifier already checks the audience, set validatetokenresource=False to silence the deprecation warning.

Affected
PackageRegistryAffectedFixed in
mcpPyPI>= 1.10.0, < 1.30.01.30.0
mcpPyPI>= 2.0.0, < 2.2.02.2.0
Downstream in the Official MCP Registry

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

  • ai.datavidence/datavidence-financialsmcp@2.1.1
  • ai.solwyn/solwynmcp@2.1.1
  • com.browser-use/browser-usemcp@2.1.1
  • com.lucidlink/mcpmcp@2.0.0
  • com.nautaai/holster-mcpmcp@1.27.2
  • io.github.abhichandra21/promptheusmcp@1.12.4
  • io.github.Alejandrehl/kainext-binance-mcpmcp@1.29.0
  • io.github.amin-ale/mcp-quickbooksmcp@1.28.1
  • io.github.AndreySukhanov/summarix-telegrammcp@1.12.4
  • io.github.AS-XS/ai-pensieve-mcpmcp@2.1.1
  • io.github.ashlesh-t/cognirepomcp@1.27.0
  • io.github.astrogilda/waitbusmcp@1.28.1
All 43 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].