MCP TypeScript SDK server advisories on audience
GitHub published several advisories on 20 Oct 2026 for MCP TypeScript SDK servers, including CVE-2026-111771 (bearer tokens issued for another service were accepted), CVE-2026-111770 (a shared transport could deliver one client's messages to another) and CVE-2026-111768 (one HTTP request could exhaust memory). Fixes are sdk 1.32.0 and server 2.3.0.
Facts read on .
For CVE-2026-111771 (medium), the advisory says the SDK's server-side bearer authentication could not check the token's audience, so a token issued for another service by the same authorization server was accepted. The MCP authorization spec requires servers to validate that tokens were issued specifically for them. The fix adds the check; the maintainers say the verifier must still be configured to use it.
CVE-2026-111770 (high) affects @modelcontextprotocol/server 2.0.0 through 2.2.0: when more than one client could reach an HTTP endpoint and the transport or server was created once at startup, messages matched on JSON-RPC id alone could reach the wrong client. stdio servers are not affected. CVE-2026-111768 (high) covers unbounded validation work; the maintainers say stdio-only servers are not affected.
A fourth record, CVE-2026-111767 (high), says experimental tasks were not tied to the session that created them. The fixed versions the advisories list are @modelcontextprotocol/sdk 1.32.0 and @modelcontextprotocol/server 2.3.0.
Sources
- GHSA-rvq5-wwqv-78pq: bearer authentication audience (github.com), read
- GHSA-jm63-cq47-j5jp: shared transport delivered messages across clients (github.com), read
- GHSA-46jr-4wx8-v453: request validation memory exhaustion (github.com), read
- GHSA-22jm-h49p-29qw: experimental tasks not tied to the session (github.com), read