Skip to main content
VulnerabilityPublished

CVE-2026-111771: @modelcontextprotocol sdk · Incorrect Authorization

Affects @modelcontextprotocol sdkSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 1.32.0 when convenient.

Data as of 5 Nov 2026, 21:19 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.16.8
Patch
Available – fixed in 1.32.0, 2.3.0, 2.0.2 +1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
modelcontextprotocoltypescript-sdkAffected
  • >=1.6.0 <1.32.0
Fixed in
  • 1.32.0
@modelcontextprotocolsdkAffected
  • >=1.6.0 <1.32.0
Fixed in
  • 1.32.0
@modelcontextprotocolserverAffected
  • >=2.0.0 <2.3.0
Fixed in
  • 2.3.0
@modelcontextprotocolexpressAffected
  • >=2.0.0 <2.0.2
Fixed in
  • 2.0.2
@modelcontextprotocolserver-legacyAffected
  • >=2.0.0 <2.3.1
Fixed in
  • 2.3.1

Description

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.

References

Community reviews

Loading reviews…