{"id":"ghsa-ghsa-rvq5-wwqv-78pq","seq":2400,"kind":"advisory","title":"MCP TypeScript SDK: Server bearer authentication accepted tokens issued for another service","url":"https://github.com/advisories/GHSA-rvq5-wwqv-78pq","permalink":"https://vulnpulse.app/items/ghsa-ghsa-rvq5-wwqv-78pq","summary":"影響: npm:@modelcontextprotocol/sdk >= 1.6.0, < 1.32.0 → 1.32.0, npm:@modelcontextprotocol/server >= 2.0.0, < 2.3.0 → 2.3.0, npm:@modelcontextprotocol/express >= 2.0.0, < 2.0.2 → 2.0.2, npm:@modelcontextprotocol/server-legacy >= 2.0.0, < 2.3.1 → 2.3.1\nSummary 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 a…","severity":"medium","techs":["nodejs"],"cves":["CVE-2026-111771"],"tags":["GHSA-rvq5-wwqv-78pq","@modelcontextprotocol/sdk","@modelcontextprotocol/server","@modelcontextprotocol/express","@modelcontextprotocol/server-legacy"],"source":{"id":"ghsa","name":"GitHub Advisory Database"},"published_at":"2026-10-20T19:43:36.000Z","fetched_at":"2026-10-21T16:17:46.637Z"}