CVE-2026-111769
Last modified
CVE-2026-111769 is a medium-severity vulnerability rated 6.5/10 on the CVSS scale. The Model Context Protocol TypeScript SDK provides TypeScript client and server implementations of the Model Context Protocol. Prior to 1.32.0 in @modelcontextprotocol/sdk and from 2.0.0 until 2.3.0 in @modelcontextprotocol/client, the HTTP client transports and OAuth client requests followed redirects to a different origin while retaining custom request headers and, for HTTP 307 or 308 responses, request bodies.
Description
The Model Context Protocol TypeScript SDK provides TypeScript client and server implementations of the Model Context Protocol. Prior to 1.32.0 in @modelcontextprotocol/sdk and from 2.0.0 until 2.3.0 in @modelcontextprotocol/client, the HTTP client transports and OAuth client requests followed redirects to a different origin while retaining custom request headers and, for HTTP 307 or 308 responses, request bodies. The affected surfaces are StreamableHTTPClientTransport, SSEClientTransport, and OAuth client functions such as auth(). The trigger is an HTTP redirect to another origin. Custom headers and mcp-session-id can be re-sent to the redirected origin. HTTP 307 and 308 redirects can also re-send the request body. OAuth request bodies can contain refresh_token and client_secret values. Current runtimes already strip the Authorization header across origins. stdio clients do not use the affected HTTP path. A malicious or compromised MCP or authorization server could therefore receive API keys, session identifiers, OAuth refresh tokens, or OAuth client secrets. Restoring unrestricted redirect following after upgrading restores the exposure. This issue is fixed in @modelcontextprotocol/sdk 1.32.0 and @modelcontextprotocol/client 2.3.0.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| modelcontextprotocol | typescript-sdk | < 1.32.0 |
| @modelcontextprotocol | sdk | < 1.32.0 |
| @modelcontextprotocol | client | >= 2.0.0, < 2.3.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-111769?
How severe is CVE-2026-111769?
How do I fix CVE-2026-111769?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-111763A2A Java SDK is the official Java SDK for the Agent2Agent (A…5.7
- CVE-2026-111764A2A Java SDK is the official Java SDK for the Agent2Agent (A…7.5
- CVE-2026-111765A2A Java SDK is the official Java SDK for the Agent2Agent (A…7.5
- CVE-2026-111766markdown-it is a Markdown parser. Prior to 14.3.3 and 15.0.3…3.7
- CVE-2026-111767MCP TypeScript SDK is the official TypeScript SDK for Model …8.6
- CVE-2026-111768The Model Context Protocol TypeScript SDK provides TypeScrip…7.5
- CVE-2026-11177Use after free in Omnibox in Google Chrome prior to 149.0.78…8.8
- CVE-2026-111770The Model Context Protocol TypeScript SDK provides TypeScrip…7.7
- CVE-2026-111771The Model Context Protocol TypeScript SDK provides TypeScrip…6.8
- CVE-2026-11178Insufficient policy enforcement in WebView in Google Chrome …4.3
- CVE-2026-11179Inappropriate implementation in ORB in Google Chrome prior t…8.8
- CVE-2026-111793Openwave Webtop Media Transcoder does not enforce administra…4.3
Are you affected by CVE-2026-111769?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
