INCIDENT MAP

Browse / MCP and Tool Server Flaws / GHSA-w2fm-25vw-vh7f

mcp-handler has a tool response leak across concurrent client sessions ('Race Condition')

GHSA-w2fm-25vw-vh7f ยท 2026-04-01 high

Class
MCP and Tool Server Flaws (filed by a model that read the advisory)
Technique
Information exposure
Also involves
Sensitive Data Disclosure
Affected
mcp-handler (npm)
CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

How it works, in short

Reusing a stateless transport across concurrent clients in the MCP SDK leaks one client's auth context and tool results to another. (Our summary, written by a model. The source text is below.)

Details

mcp-handler versions prior to 1.1.0 accepted @modelcontextprotocol/sdk < 1.26.0 as a peer dependency. That SDK version contains a vulnerability [CVE-2026-25536] that causes concurrent requests from different clients to share server-side state including authentication context and tool execution results when a StreamableHTTPServerTransport instance is reused across requests.

Note: This is _not_ a vulnerability in mcp-handler itself. The root cause is in the peer dependency @modelcontextprotocol/sdk.

Impact

A low-privileged attacker making concurrent requests to an mcp-handler endpoint can read another client's session data, including authentication information and tool execution state. This is a confidentiality breach with potential for limited integrity impact.

Root Cause: CVE-2026-25536 in @modelcontextprotocol/sdk < 1.26.0. The SDK did not prevent reuse of stateless transports across client connections.

Patches

Upgrade to mcp-handler@1.1.0. This release raises the minimum peer dependency to @modelcontextprotocol/sdk@>=1.26.0, which contains the fix for CVE-2026-25536.

Workarounds

References

Source: GitHub Advisory Database, used under CC BY 4.0.