UTC
Medium

RMCP: Custom HTTP headers leak to cross-origin redirect targets

CVE-2026-64684 · GHSA-9g45-5xwm-f3wc · published 2026-09-17

Severity
Medium
CVSS score
6.8
Chance of exploitation (EPSS)
0.50%
Fixed in
2.1.0
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Partial
  • CISA SSVC
What it is

The rmcp crate's StreamableHttpClientTransport forwards caller-supplied custom HTTP headers (such as X-API-Key, X-Auth-Token, Api-Key) to cross-origin redirect targets. The defaulthttpclient() function builds a reqwest::Client without a redirect policy override, so the default limited(10) policy follows 307/308 redirects and forwards all per-request headers except Authorization, Cookie, and Proxy-Authorization. Custom auth headers injected via are not classified as sensitive and are therefore forwarded verbatim to any redirect target — including an attacker-controlled server.

What to do

Upgrade rmcp to 2.1.0 or later.

In defaulthttpclient(), disable automatic redirect following: The transport can then inspect 3xx responses and decide whether to follow, stripping sensitive headers before doing so. Alternatively, use to remove auth headers before the redirect is followed.

Affected
PackageRegistryAffectedFixed in
rmcpcrates.io< 2.1.02.1.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].