threatdeck
Live 14:45 UTC ·

AI Stack Alert Medium CVE-2026-111771 For AppSec, AI Eng, SOC / IR, CISO AI-assisted

CVE-2026-111771: MCP TypeScript SDK bearer auth accepts tokens issued for other services

The Model Context Protocol TypeScript SDK did not enforce token audience in server-side HTTP bearer authentication. A valid access token issued for a different service could authenticate to an affected MCP server. Fixed in @modelcontextprotocol/sdk 1.32.0, @modelcontextprotocol/server 2.3.0, @modelcontextprotocol/express 2.0.2, and @modelcontextprotocol/server-legacy 2.3.1. CVSS base score is 6.8.

Why it matters

Organizations running affected MCP servers whose authorization server issues tokens for multiple services are exposed. An attacker holding a token for another service could gain the confidentiality and integrity capabilities granted to authenticated callers.

Do this

  1. Upgrade @modelcontextprotocol/sdk to 1.32.0, @modelcontextprotocol/server to 2.3.0, @modelcontextprotocol/express to 2.0.2, or @modelcontextprotocol/server-legacy to 2.3.1, matching the package in use.
  2. After upgrading, enable audience validation in the bearer auth configuration and supply the expected token audience together. Enabling only the expected audience check causes every request to return HTTP 401.
  3. Review verifyAccessToken() implementations. If aud is not validated there, confirm the upgraded audience validation is enabled and correct.
  4. Check whether the authorization server issues tokens for multiple services. If it does, prioritize this patch and review access logs for tokens with unexpected audiences.

Exploit Clock

Exploitation unlikely (for now)

  • EPSS 0.54%

Signals

  • NoCISA KEV
  • 6.8CVSS
  • 0.54%EPSS
  • NoPublic PoC
  • 27/100Priority
  • 80%Confidence

Evidence

“server-side bearer authentication could accept a valid access token issued for a different service because the SDK did not enforce the token audience”

NVD (AI keyword search)

“Upgrading alone leaves the new audience validation disabled. Operators must enable audience validation and provide the token audience together.”

NVD (AI keyword search)

“Enabling only the expected audience check causes every request to receive HTTP 401.”

NVD (AI keyword search)

Sources

Affected / related

@modelcontextprotocol/sdk, @modelcontextprotocol/server, @modelcontextprotocol/express, @modelcontextprotocol/server-legacy, OAuth token audience validation bypass

Published 2026-11-05 21:18 UTC · updated 2026-11-08 02:27 UTC · AI-assisted summary, checked against quoted sources · How we score

Following

Follow the vendors, products, AI tools, techniques and actors you care about. Matching stories, CVEs and exploited bugs are marked, a Following tab appears in the feed, and returning visits show what changed. Saved only in this browser.

Presets

Get updates

A personal RSS feed of new stories on everything you follow. Paste it into any feed reader, Slack or Teams RSS app.