• Sources: primary, primary, primary
  • Summary: RUSTSEC-2026-0457 (GHSA-5p52-q7pq-9fq2) says the rmcp OAuth client from 2.0.0 until 3.7.0 checked only host strings, so a malicious MCP server could steer discovery to a hostname resolving to an internal address, and token and registration endpoints were not checked at all. RUSTSEC-2026-0461, rated CVSS 7.5, says StreamableHttpService from 3.0.0 until 3.6.0 cached tool lookups by name with no size limit, even for rejected requests, so unauthenticated clients could exhaust server memory. RUSTSEC-2026-0462 covers unbounded response body buffering in Streamable HTTP clients.
  • Why it matters: Rust MCP clients and servers built on rmcp should move to 3.7.0, and code that passes a custom OAuth HTTP client must enforce its own outbound address policy.
  • Background: The Model Context Protocol (MCP) lets AI agents call tools exposed by servers, and Streamable HTTP is its HTTP transport. Server-side request forgery (SSRF) here means a hostile server tricks the client into sending requests to internal services it can reach, such as unauthenticated admin endpoints. The fix resolves hostnames and applies the address policy to every resolved address and redirect, rather than inspecting the URL text.