Skip to content

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

MediumCVSS 6.8 EPSS 0.50%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial
Technology
Red Hat

Description

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.

Upgrade path

4 packages: 1 fixed, 2 with no fix yet.

PackageAffectedFixed inStatus
redhat/goose(Red Hat enterprise_linux 10) All versions No fix listed No fix yet
redhat/goose(Red Hat enterprise_linux 9) All versions No fix listed No fix yet
crates.io rmcp(crates.io) < 2.1.0 2.1.0 Fixed
modelcontextprotocol rust-sdk = < 2.1.0 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
crates.io rmcp(crates.io) < 2.1.0 2.1.0
modelcontextprotocol rust-sdk = < 2.1.0 No fix listed
redhat/goose(Red Hat:enterprise_linux:10) All versions No fix listed
redhat/goose(Red Hat:enterprise_linux:9) All versions No fix listed

References