NVD published 5 Nov 2026
CVE-2026-111770
1 public exploit.
The Model Context Protocol TypeScript SDK provides TypeScript client and server implementations of the Model Context Protocol. From 2.0.0 until 2.3.0 in @modelcontextprotocol/server, applications that shared one stateless HTTP transport or one McpServer or Server instance among multiple clients could deliver responses and notifications to the wrong client. The affected surface is an MCP server reached over HTTP by multiple clients. The trigger is reuse of one stateless transport or server instance. Messages were associated with a connection using only the JSON-RPC request identifier. SDK clients start request identifiers at zero, so collisions occur in normal operation. Cross-client delivery exposes one client's responses and notifications to another client. The issue requires an HTTP endpoint reachable by more than one client and an application that constructs the server or transport once at startup instead of once per request or session. stdio servers and factory-created per-call servers are not affected. Upgrading causes reused instances to fail and therefore requires an application code change. This issue is fixed in @modelcontextprotocol/server 2.3.0.
Signals
- KEV, exploited in the wild
- no
- EPSS, 30-day forecast
- 0.4%, 31th percentile (as of 18 Nov 2026)
- CVSS, NVD, HIGH
- 7.7
- Vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H
- Internet exposure
- not stated
Not in CISA's catalogue as of the last daily pull. Absence is not proof of safety.
Timeline 21 Oct 2026 to today
- First PoC
- Disclosed+15 d
15 days from the first proof of concept to disclosure
Indicators none tied yet
No threat feed has tied an indicator to this CVE yet. Checked every six hours.
On the wire 1 dispatch
Public exploit code 1 known · links only
GitHub PoCs 1Metasploit 0Exploit-DB 0
GitHub PoCs, by trust then stars1
- hahahahahahahahah6/mcp-idprobeTrust ok 1000 stars
Runtime probe for MCP cross-tenant response leaking via JSON-RPC id collision (CVE-2026-111770)
created 21 Oct 2026
Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.