MCP TypeScript SDK OAuth client advisory (CVE-2026-104850)
GitHub published advisory GHSA-6qxp-vccf-f47h (CVE-2026-104850, high severity) on 6 Oct 2026. In affected TypeScript SDK versions, the OAuth client let an MCP server choose which authorization server received the client's credentials, with no user interaction. Fixes are @modelcontextprotocol/sdk 1.31.0 and @modelcontextprotocol/client 2.2.0.
Facts read on .
The advisory says an application is affected if it uses the SDK's OAuth client over HTTP and may connect to an MCP server it does not fully trust while holding credentials for a legitimate authorization server. Servers built with the SDK and stdio clients are not affected. Affected ranges are @modelcontextprotocol/sdk 1.12.0 through 1.30.1 and @modelcontextprotocol/client 2.0.0 through 2.1.0, with conditions listed in the record.
The fix records the authorization server as the issuer on saved credentials and refuses to send them to a different one. The maintainers add that upgrading is not always enough: bundled providers need an expectedIssuer value, and credentials saved before the upgrade without an issuer must be given one or cleared so users sign in again.
The spec's security best practices page lists OAuth discovery URLs among the inputs a client must not trust blindly, so this advisory is a concrete case of a client acting on server-supplied metadata.
Sources
- GHSA-6qxp-vccf-f47h: MCP TypeScript SDK OAuth client (github.com), read
- MCP Security Best Practices, 2026-07-28 (modelcontextprotocol.io), read