INCIDENT MAP

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

MCP TypeScript SDK: Server bearer authentication accepted tokens issued for another service

CVE-2026-111771 ยท 2026-10-20 moderate

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

How it works, in short

The MCP TypeScript SDK's bearer auth never checked token audience, so tokens issued for other services were 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 requireBearerAuth() or verifyBearerToken(), its authorization server also issues tokens for other services, and your verifyAccessToken() does not check the token's audience (aud) itself.

Affected versions:

Fix

Upgrade to:

Upgrading alone changes nothing. The patched versions add an expectedResource setting that is off by default. 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 you cannot upgrade yet, reject any token whose aud does not include your server inside verifyAccessToken(). That closes the issue on every version.

References

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