CVE-2026-116684

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

Published Oct 27, 2026 CVSS 3.1 · 6.8 Medium EPSS < 1% KEV · Not listed
Description
The Model Context Protocol Python SDK is the official Python SDK for Model Context Protocol servers and clients. From 1.10.0 until 1.30.0 and 2.2.0, server-side bearer authentication configured through AuthSettings with token_verifier accepts a valid token issued for another service when the authorization server serves multiple resources and the TokenVerifier does not independently validate the aud audience. This resource-confusion flaw lets a token holder authenticate to the wrong MCP server and exercise that token's resulting access. This issue is fixed in versions 1.30.0 and 2.2.0.

Analysis

AI-generated

Technical impact

The Model Context Protocol Python SDK performs server‑side bearer authentication using a TokenVerifier that does not independently validate the token’s audience (aud) claim when the authorization server issues tokens for multiple resource servers. As a result, a bearer token issued for one MCP server can be accepted by another server, allowing the holder to authenticate to an unintended resource and exercise the permissions encoded in that token. This flaw effectively bypasses intended audience constraints, enabling an attacker who holds a valid token for one server to gain unauthorized access to a different MCP server, potentially exposing sensitive data or operations governed by that resource.

Affected Systems

The vulnerability affects Model Context Protocol Python SDK releases from version 1.10.0 up to (but not including) 1.30.0, as well as 2.x releases prior to 2.2.0. The fix was introduced in SDK 1.30.0 and 2.2.0. Any deployments using these earlier versions are exposed.

Risk and Exploitability

The CVSS score of 6.8 indicates a serious severity, and the EPSS score of less than 1% suggests a very low probability of exploitation at the time of analysis. The vulnerability is not listed in CISA’s KEV catalog. The likely attack vector is a simple token replay across resource servers: an adversary with a valid token for one resource can reuse it against another MCP server because the SDK does not enforce the audience claim, making the exploit trivial for whoever can obtain or intercept a token.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the SDK to at least version 1.30.0 for the 1.x series or version 2.2.0 for the 2.x series and redeploy in all environments that use MCP server authentication
  • Replace any legacy SDK copies with the updated package to ensure the source code incorporates the audience validation fix
  • If an immediate upgrade is not possible, add client‑side code that verifies the aud claim matches the intended resource before accepting a token as valid

Generated by OpenCVE AI on October 29, 2026 at 14:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-w4fh-qvv9-3v23 Model Context Protocol Python SDK: Server bearer-token authentication accepts tokens issued for a different resource server
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Modelcontextprotocol
Modelcontextprotocol python-sdk
Vendors & Products Modelcontextprotocol
Modelcontextprotocol python-sdk
Type Values Removed Values Added
Description The Model Context Protocol Python SDK is the official Python SDK for Model Context Protocol servers and clients. From 1.10.0 until 1.30.0 and 2.2.0, server-side bearer authentication configured through AuthSettings with token_verifier accepts a valid token issued for another service when the authorization server serves multiple resources and the TokenVerifier does not independently validate the aud audience. This resource-confusion flaw lets a token holder authenticate to the wrong MCP server and exercise that token's resulting access. This issue is fixed in versions 1.30.0 and 2.2.0.
Title Model Context Protocol Python SDK: Server bearer-token authentication accepts tokens issued for a different resource server
Weaknesses CWE-863
References
Metrics cvssV3_1

{'score': 6.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses
  • CWE-303

    Incorrect Implementation of Authentication Algorithm

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 2, 2026, 7:40 PM
Reserved
Oct 26, 2026, 8:00 PM
Status
Awaiting Analysis
Published
Oct 27, 2026, 8:17 PM
Modified
Nov 2, 2026, 8:17 PM
Severity
Moderate
Public date
Oct 27, 2026, 7:12 PM