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

Summary

The imported advisory is rated medium severity. It identifies 1 affected package; whether you are affected depends on your installed version. It is not listed in the imported CISA KEV data; that does not establish that exploitation has not occurred.

Summary by cve.new · CC BY 4.0

Original source description

Summary

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.

Am I affected?

Yes, if your HTTP server uses the SDK's bearer authentication (auth=AuthSettings(...) with token_verifier=), its authorization server also issues tokens for other services, and your TokenVerifier does not check the token's audience (aud) itself.

Affected versions:

mcp 1.10.0 through 1.29.1
mcp 2.0.0 through 2.1.1

Fix

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 validate_token_resource setting that is off unless you set it. To turn the check on, make both of these changes together:

Set validate_token_resource=True in AuthSettings, with resource_server_url set to the audience your authorization server puts in tokens for your server.
Return the token's audience from verify_token() 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 validate_token_resource=False to silence the deprecation warning. The setting will default to True in 3.0.

If you cannot upgrade yet, reject any token whose aud does not include your server inside verify_token(). That closes the issue on every version.

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

mcp PyPI

Ecosystem versions

From 2.0.0 before 2.2.0

Fixed in 2.2.0

4 explicitly affected versions

2.0.0, 2.0.1, 2.1.0, 2.1.1

View affected-version evidence

{
  "ranges": [
    {
      "events": [
        {
          "introduced": "2.0.0"
        },
        {
          "fixed": "2.2.0"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "2.0.0",
    "2.0.1",
    "2.1.0",
    "2.1.1"
  ]
}

mcp PyPI

Ecosystem versions

From 1.10.0 before 1.30.0

Fixed in 1.30.0

36 explicitly affected versions

1.10.0, 1.10.1, 1.11.0, 1.12.0, 1.12.1, 1.12.2, 1.12.3, 1.12.4, 1.13.0, 1.13.1, 1.14.0, 1.14.1, 1.15.0, 1.16.0, 1.17.0, 1.18.0, 1.19.0, 1.20.0, 1.21.0, 1.21.1, 1.21.2, 1.22.0, 1.23.0, 1.23.1, 1.23.2, 1.23.3, 1.24.0, 1.25.0, 1.26.0, 1.27.0, 1.27.1, 1.27.2, 1.28.0, 1.28.1, 1.29.0, 1.29.1

View affected-version evidence

{
  "ranges": [
    {
      "events": [
        {
          "introduced": "1.10.0"
        },
        {
          "fixed": "1.30.0"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "1.10.0",
    "1.10.1",
    "1.11.0",
    "1.12.0",
    "1.12.1",
    "1.12.2",
    "1.12.3",
    "1.12.4",
    "1.13.0",
    "1.13.1",
    "1.14.0",
    "1.14.1",
    "1.15.0",
    "1.16.0",
    "1.17.0",
    "1.18.0",
    "1.19.0",
    "1.20.0",
    "1.21.0",
    "1.21.1",
    "1.21.2",
    "1.22.0",
    "1.23.0",
    "1.23.1",
    "1.23.2",
    "1.23.3",
    "1.24.0",
    "1.25.0",
    "1.26.0",
    "1.27.0",
    "1.27.1",
    "1.27.2",
    "1.28.0",
    "1.28.1",
    "1.29.0",
    "1.29.1"
  ]
}

Set up in your agent.

Investigate in your agent.

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

Summary

Original source description

Summary

Am I affected?

Fix

Affected packages

References