<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 20:38:10 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-64684</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-64684</link>
      <description>&lt;p&gt;RMCP is an official Rust SDK for the Model Context Protocol. Prior to 2.1.0, the rmcp crate&amp;#39;s StreamableHttpClientTransport in crates/rmcp/src/transport/common/reqwest/streamable_http_client.rs builds its default_http_client with reqwest&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;RMCP is an official Rust SDK for the Model Context Protocol. Prior to 2.1.0, the rmcp crate&amp;#39;s StreamableHttpClientTransport in crates/rmcp/src/transport/common/reqwest/streamable_http_client.rs builds its default_http_client with reqwest&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-64684</guid>
    </item>
    <item>
      <title>GHSA-9g45-5xwm-f3wc — RMCP: Custom HTTP headers leak to cross-origin redirect targets</title>
      <link>https://db.gcve.eu/vuln/ghsa-9g45-5xwm-f3wc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: rmcp&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `rmcp` crate&amp;#39;s `StreamableHttpClientTransport` forwards caller-supplied custom HTTP headers (such as `X-API-Key`, `X-Auth-Token`, `Api-Key`) to cross-origin redirect targets. The `default_http_client()` 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 `StreamableHttpClientTransportConfig.custom_headers` are not classified as sensitive and are therefore forwarded verbatim to any redirect target — including an attacker-controlled server.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;- Repository: `github.com/modelcontextprotocol/rust-sdk`
- Crate: `rmcp`
- Commit tested: `c330fede90e4729c234f8e87fdbc5ea27a1dd10c` (HEAD, 2026-05-21)&lt;/p&gt;
&lt;p&gt;## Vulnerability&lt;/p&gt;
&lt;p&gt;**File:** `crates/rmcp/src/transport/common/reqwest/streamable_http_client.rs`&lt;/p&gt;
&lt;p&gt;**Root cause 1 — no redirect policy override:**&lt;/p&gt;
&lt;p&gt;```rust
// Lines 302-307
fn default_http_client() -&amp;gt; reqwest::Client {
    reqwest::Client::builder()
        .pool_max_idle_per_host(0)
        .build()
        .expect(&amp;#34;failed to build default reqwest client&amp;#34;)
}
```&lt;/p&gt;
&lt;p&gt;No `.redirect(reqwest::redirect::Policy::none())` call. The default `limited(10)` policy follows up to 10 redirects and, on cross-origin redirects, strips only `Authorization`, `Cookie`, and `Proxy-Authorization`.&lt;/p&gt;
&lt;p&gt;**Root cause 2 — custom headers not sensitivity-marked:**&lt;/p&gt;
&lt;p&gt;```rust…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: rmcp&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `rmcp` crate&amp;#39;s `StreamableHttpClientTransport` forwards caller-supplied custom HTTP headers (such as `X-API-Key`, `X-Auth-Token`, `Api-Key`) to cross-origin redirect targets. The `default_http_client()` 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 `StreamableHttpClientTransportConfig.custom_headers` are not classified as sensitive and are therefore forwarded verbatim to any redirect target — including an attacker-controlled server.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;- Repository: `github.com/modelcontextprotocol/rust-sdk`
- Crate: `rmcp`
- Commit tested: `c330fede90e4729c234f8e87fdbc5ea27a1dd10c` (HEAD, 2026-05-21)&lt;/p&gt;
&lt;p&gt;## Vulnerability&lt;/p&gt;
&lt;p&gt;**File:** `crates/rmcp/src/transport/common/reqwest/streamable_http_client.rs`&lt;/p&gt;
&lt;p&gt;**Root cause 1 — no redirect policy override:**&lt;/p&gt;
&lt;p&gt;```rust
// Lines 302-307
fn default_http_client() -&amp;gt; reqwest::Client {
    reqwest::Client::builder()
        .pool_max_idle_per_host(0)
        .build()
        .expect(&amp;#34;failed to build default reqwest client&amp;#34;)
}
```&lt;/p&gt;
&lt;p&gt;No `.redirect(reqwest::redirect::Policy::none())` call. The default `limited(10)` policy follows up to 10 redirects and, on cross-origin redirects, strips only `Authorization`, `Cookie`, and `Proxy-Authorization`.&lt;/p&gt;
&lt;p&gt;**Root cause 2 — custom headers not sensitivity-marked:**&lt;/p&gt;
&lt;p&gt;```rust…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-9g45-5xwm-f3wc</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11849-1 — openai-codex-0.155.1-1.1 on GA media</title>
      <link>https://db.gcve.eu/vuln/opensuse-su-2026:11849-1</link>
      <description>&lt;p&gt;openai-codex-0.155.1-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;openai-codex-0.155.1-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/opensuse-su-2026:11849-1</guid>
    </item>
  </channel>
</rss>
