Medium

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

  • Disclosed: 27.10.2026
  • Updated: 27.10.2026 23:17

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:

  1. Set validate_token_resource=True in AuthSettings, with resource_server_url set to the audience your authorization server puts in tokens for your server.
  2. 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 software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) mcp >= 2.0.0, < 2.2.0, >= 1.10.0, < 1.30.0 2.2.0, 1.30.0

References

CVSS score 6.8/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Weakness (CWE)
CWE-863
Platform
Python (PyPI)
Package
mcp
Disclosed
27.10.2026
Updated
27.10.2026 23:17

Sources and licenses

OSV / GitHub Advisory Database - GHSA-w4fh-qvv9-3v23 - CC BY 4.0

Vulnerability history: mcp

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (11) in the archive
Total entries
11
First → latest
07.2025 11.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 7
  • Medium 4

Disclosures per year

  1. 2025: 3
  2. 2026: 8
Severity:
  1. High · 7.5 CVE-2026-115563 >= 2.0.0a1, < 2.2.0, >= 1.9.1, < 1.30.0 2.2.0, 1.30.0
  2. Model Context Protocol Python SDK: Server bearer-token authentication accepts tokens issued for a different resource server this entry
    Medium · 6.8 CVE-2026-116684 >= 2.0.0, < 2.2.0, >= 1.10.0, < 1.30.0 2.2.0, 1.30.0

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.