CVE-2026-111768
Last modified
CVE-2026-111768 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. The Model Context Protocol TypeScript SDK provides TypeScript client and server implementations of the Model Context Protocol. From 1.3.0 until 1.32.0 in @modelcontextprotocol/sdk and from 2.0.0 until 2.3.0 in @modelcontextprotocol/server, HTTP servers did not enforce a limit on the number of array elements and object keys validated in one request.
Description
The Model Context Protocol TypeScript SDK provides TypeScript client and server implementations of the Model Context Protocol. From 1.3.0 until 1.32.0 in @modelcontextprotocol/sdk and from 2.0.0 until 2.3.0 in @modelcontextprotocol/server, HTTP servers did not enforce a limit on the number of array elements and object keys validated in one request. The affected surface is validation of HTTP requests containing arrays or object keys. The trigger is an array-element or object-key validation workload large enough to exhaust memory while remaining within the request size limit. A single request within the default 4 MiB limit can terminate the process with JavaScript heap exhaustion. No credentials are required unless the application authenticates before SDK processing. Tools accepting arrays or records carry the greatest risk. stdio-only servers do not expose the HTTP request path. Upgrading alone does not enable the new validation bound. Operators must configure both a tool-input element bound and an appropriate request body size limit. This issue is fixed in @modelcontextprotocol/sdk 1.32.0 and @modelcontextprotocol/server 2.3.0.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| modelcontextprotocol | typescript-sdk | >= 1.3.0, < 1.32.0 |
| @modelcontextprotocol | server | >= 2.0.0, < 2.3.0 |
| @modelcontextprotocol | sdk | >= 1.3.0, < 1.32.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-111768?
How severe is CVE-2026-111768?
How do I fix CVE-2026-111768?
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-111762A2A Java SDK is the official Java SDK for the Agent2Agent (A…5.7
- 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-111769The Model Context Protocol TypeScript SDK provides TypeScrip…6.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
Are you affected by CVE-2026-111768?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
