Intel

AIKIDO-2026-156139

@modelcontextprotocol/sdk is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor

CVE-2026-111769Published Oct 9, 2026
October 9, 2026

65

CVE Score

Medium

Exposure of Sensitive Information to an Unauthorized Actor

Are you affected? Scan for Free

TL;DR

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.

How do I fix this?

Upgrade the @modelcontextprotocol/sdk library to the patch version.

Who does this affect?

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.

Versions

0.4.0 - 1.31.0

Fixed in 1.32.0

Background info

@modelcontextprotocol/sdk is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor in versions 0.4.0 - 1.31.0.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea