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
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.
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.
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
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- HighModel Context Protocol Python SDK: OAuth client could send credentials to an authorization server chosen by the MCP servermcp, mcp
- HighHTTP server transports and OAuth endpoints read request bodies with no size limitmcp, mcp
- HighMCP Python SDK: Experimental task handlers allow any client to access and cancel other clients' tasksmcp
- HighMCP Python SDK: HTTP transports serve session requests without verifying the authenticated principalmcp
- HighMCP Python SDK: WebSocket server transport does not support Host/Origin validationmcp
- HighModel Context Protocol (MCP) Python SDK does not enable DNS rebinding protection by defaultmcp
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.