CVE-2026-64684

published 16 Sep 2026 · updated 19 Sep 2026

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

6.8MediumCVSS 6.8EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

RMCP is an official Rust SDK for the Model Context Protocol. Prior to 2.1.0, the rmcp crate's StreamableHttpClientTransport in crates/rmcp/src/transport/common/reqwest/streamable_http_client.rs builds its default_http_client with reqwest's automatic redirect policy and applies caller-supplied values from StreamableHttpClientTransportConfig.custom_headers without marking them as sensitive. When a malicious or compromised MCP endpoint returns a cross-origin 307 or 308 redirect, reqwest follows the redirect and apply_custom_headers causes custom API keys or authentication tokens to be replayed to the new origin, where an attacker can capture and reuse them. The separate auth_header path is not affected because it uses the standard Authorization header, which reqwest strips on cross-origin redirects. This issue is fixed in version 2.1.0.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
modelcontextprotocol<2.1.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-64684 severity on Zeptric[![CVE-2026-64684](https://zeptric.io/badge/cve/CVE-2026-64684.svg)](https://zeptric.io/cve/CVE-2026-64684)