Bug 2535732 (CVE-2026-64684) - CVE-2026-64684 rmcp: RMCP: Sensitive HTTP headers leaked during cross-origin redirects
Summary: CVE-2026-64684 rmcp: RMCP: Sensitive HTTP headers leaked during cross-origin ...
Keywords:
Status: NEW
Alias: CVE-2026-64684
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2535856 2535857
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-16 21:29 UTC by OSIDB Bzimport
Modified: 2026-09-17 08:36 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-16 21:29:51 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.