CVE-2026-111771
Published:November 05, 2026
Updated:November 18, 2026
The Model Context Protocol TypeScript SDK provides TypeScript client and server implementations of the Model Context Protocol. From 1.6.0 until 1.32.0 in @modelcontextprotocol/sdk, from 2.0.0 until 2.3.0 in @modelcontextprotocol/server, from 2.0.0 until 2.0.2 in @modelcontextprotocol/express, and from 2.0.0 until 2.3.1 in @modelcontextprotocol/server-legacy, server-side bearer authentication could accept a valid access token issued for a different service because the SDK did not enforce the token audience. The affected surface is server-side HTTP bearer authentication. The trigger is a valid token whose audience names another service. The authorization server must issue tokens for multiple services, and the application's verifyAccessToken() must not independently validate aud. Applications already validating aud inside verifyAccessToken() are not affected. An attacker with a token for another service could authenticate to the MCP server and obtain the confidentiality and integrity capabilities granted to an authenticated caller. Upgrading alone leaves the new audience validation disabled. Operators must enable audience validation and provide the token audience together. Enabling only the expected audience check causes every request to receive HTTP 401. This issue is fixed in @modelcontextprotocol/sdk 1.32.0, @modelcontextprotocol/server 2.3.0, @modelcontextprotocol/express 2.0.2, and @modelcontextprotocol/server-legacy 2.3.1.
Affected Packages
https://github.com/modelcontextprotocol/typescript-sdk.git (GITHUB):
Affected version(s) >=@modelcontextprotocol/server-legacy@2.0.0-alpha.3 <@modelcontextprotocol/server-legacy@2.3.1Fix Suggestion:
Update to version @modelcontextprotocol/server-legacy@2.3.1https://github.com/modelcontextprotocol/typescript-sdk.git (GITHUB):
Affected version(s) >=@modelcontextprotocol/server@2.0.0-beta.3 <@modelcontextprotocol/server@2.3.0Fix Suggestion:
Update to version @modelcontextprotocol/server@2.3.0https://github.com/modelcontextprotocol/typescript-sdk.git (GITHUB):
Affected version(s) >=1.6.0 <1.32.0Fix Suggestion:
Update to version 1.32.0https://github.com/modelcontextprotocol/typescript-sdk.git (GITHUB):
Affected version(s) >=@modelcontextprotocol/express@2.0.0-alpha.4 <@modelcontextprotocol/express@2.0.2Fix Suggestion:
Update to version @modelcontextprotocol/express@2.0.2https://github.com/modelcontextprotocol/typescript-sdk.git (GITHUB):
Affected version(s) >=v2.0.0-beta.1 <v2.3.1Fix Suggestion:
Update to version v2.3.1@modelcontextprotocol/express (NPM):
Affected version(s) >=2.0.0 <2.0.2 || >=2.0.0-alpha.3 <2.0.2Fix Suggestion:
Update to version 2.0.2@modelcontextprotocol/sdk (NPM):
Affected version(s) >=1.6.0 <1.32.0Fix Suggestion:
Update to version 1.32.0@modelcontextprotocol/server (NPM):
Affected version(s) >=2.0.0 <2.3.0 || >=2.0.0-beta.3 <2.3.0Fix Suggestion:
Update to version 2.3.0@modelcontextprotocol/server-legacy (NPM):
Affected version(s) >=2.0.0 <2.3.1 || >=2.0.0-alpha.2 <2.3.1Fix Suggestion:
Update to version 2.3.1Related ResourcesĀ (14)
Do you need more information?
Contact UsCVSS v4
Base Score:
7.6
Attack Vector
NETWORK
Attack Complexity
HIGH
Attack Requirements
NONE
Privileges Required
LOW
User Interaction
NONE
Vulnerable System Confidentiality
HIGH
Vulnerable System Integrity
HIGH
Vulnerable System Availability
NONE
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
6.8
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Weakness Type (CWE)
Incorrect Authorization
EPSS
Base Score:
0.54