INCIDENT MAP

Browse / MCP and Tool Server Flaws / CVE-2026-116684

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

CVE-2026-116684 ยท 2026-10-27 moderate

Class
MCP and Tool Server Flaws (filed by a model that read the advisory)
Technique
Authentication and access control
Affected
mcp (PyPI)
Gets past
Authorisation check
CVSS
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
0.4% chance of exploitation in 30 days

How it works, in short

The bearer token verifier does not check the audience, so tokens issued for other services are accepted by the MCP server. (Our summary, written by a model. The source text is below.)

Details

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:

Fix

Upgrade to:

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:

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.

References

Source: GitHub Advisory Database, used under CC BY 4.0.