INCIDENT MAP

Browse / MCP and Tool Server Flaws / CVE-2026-104850

MCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server

CVE-2026-104850 ยท 2026-10-06 high

Class
MCP and Tool Server Flaws (filed by a model that read the advisory)
Technique
Data exfiltration
Also involves
Sensitive Data Disclosure
Affected
@modelcontextprotocol/sdk (npm)
CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.3% chance of exploitation in 30 days

How it works, in short

A malicious MCP server can choose its own authorization server, so the client automatically sends stored refresh tokens and client secrets to it. (Our summary, written by a model. The source text is below.)

Details

Summary

In affected versions, the SDK's OAuth client let the MCP server decide which authorization server received the client's OAuth credentials. Credentials were not tied to the authorization server they belong to.

A malicious or compromised MCP server could name its own authorization server. With no user interaction, the client would send it:

Am I affected?

Yes, if both of these hold:

Affected versions:

Not affected:

Fix

Upgrade to:

The client now records the authorization server as issuer on saved credentials and does not send them to a different one. The user signs in again, or the call throws.

In the following cases, upgrading to the patched version is not enough. You also need to make a change:

Not covered by this fix:

If an affected client may have connected to an untrusted MCP server, rotate its client secret or signing key and revoke its tokens.

If you cannot upgrade yet, connect OAuth clients only to MCP servers you trust. 2.0.0 and 2.1.0 already accept expectedIssuer.

References

Source: GitHub Advisory Database, used under CC BY 4.0.