UTC
High

RMCP: Unauthenticated permanent session-table leak in rmcp Streamable HTTP server transport leads to remote denial-of-service

CVE-2026-63128 · GHSA-9pj6-vhgr-3mwh · published 2026-09-16

Severity
High
CVSS score
7.5
Chance of exploitation (EPSS)
0.53%
Fixed in
2.0.0
  • Exploitation Public proof of concept
  • Automatable No
  • Technical impact Partial
  • CISA SSVC
What it is

Attack vector: Network (AV:N). The listener binds a TCP port; the default accepts anything reaching it over the loopback interface. In the dominant deployment model — a Streamable HTTP MCP server embedded into an IDE or local agent — any co-resident process on the host is a candidate attacker. In LAN deployments where the operator widened allowedhosts to a public hostname, the attack is reachable from the network. Authentication required: None. User interaction required: None. Result: Denial of Service. Memory grows linearly with attacker request volume (~400–550 bytes per leaked entry, including the SessionId Arc , the LocalSessionHandle struct, and the half-dropped mpsc channel Inner).

What to do

Upgrade rmcp to 2.0.0 or later.

Two minimally invasive options. Both have been considered against the existing API; the maintainers will know which fits better with the internal contracts. 1. Validate before allocating. Move the line. Reject non-initialize bodies with 422 before any state is created. This removes a class of bugs rather than patching one path. The downside is that validateheadermatchesinitbody currently reads initreq.params.protocolversion, so the InitializeRequest discriminant has to be deconstructed earlier — a small refactor. 2. RAII guard for the session. Wrap the sessionid returned by createsession in a guard whose Drop impl spawns a close_session call.

Affected
PackageRegistryAffectedFixed in
rmcpcrates.io< 2.0.02.0.0

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].