Improper Cross-boundary Removal of Sensitive Data Affecting goose package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.5% (41st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-GOOSE-19890664
  • published18 Sept 2026
  • disclosed16 Sept 2026

Introduced: 16 Sep 2026

NewCVE-2026-64684  (opens in a new tab)
CWE-212  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 goose.

NVD Description

Note: Versions mentioned in the description apply only to the upstream goose package and not the goose package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1