@modelcontextprotocol/sdk is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
65
Medium Risk
The SDK's HTTP client transports and OAuth client functions follow redirects to any origin, including cross origin destinations controlled by the server or authorization server being contacted. On a cross origin redirect, the new origin receives custom request headers such as an X-API-Key and the mcp-session-id header, and a 307 or 308 redirect also forwards the request body, including OAuth refresh_token and client_secret values. stdio clients are not affected; only StreamableHTTPClientTransport, SSEClientTransport, and the OAuth client functions such as auth() follow these redirects. The fix follows redirects only within the same origin, and does not follow them at all in browsers.
You are affected if you are using a version that falls within the vulnerable range and your application uses StreamableHTTPClientTransport, SSEClientTransport, or the SDK's OAuth client functions.
@modelcontextprotocol/sdk is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor in versions 0.0.1 - 1.31.0.
Upgrade the @modelcontextprotocol/sdk library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.