Skip to main content
VulnerabilityPublished

rmcp OAuth client fetches server-controlled resource_metadata URLs

Affects rmcpSource GCVE Database

0

CVSS 6.3 Medium : upgrade to 2.0.0 when convenient.

Data as of 2 Oct 2026, 17:50 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.0.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

What to do

Upgrade rmcp to 2.0.0.

Affected software

ProductAffectedFixed in
crates.iormcpAffected
  • <2.0.0
Fixed in
  • 2.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available to address this vulnerability. The fix involves validating that the resource_metadata URL is same-origin with the MCP server URL and rejecting URLs that point to loopback, link-local, RFC 1918, unique-local IPv6, or known cloud metadata hostnames. Non-HTTP(S) schemes should also be rejected. These validations should apply to redirect targets and any subsequent metadata URLs. Users should update to a patched version of the rmcp crate to mitigate this SSRF risk.

Description

The rmcp OAuth client in the modelcontextprotocol rust-sdk accepts a server-controlled resource_metadata URL from the WWW-Authenticate header and fetches it without validating origin or blocking internal network addresses. This allows an attacker-controlled or compromised MCP server to induce the client to make HTTP requests to internal or cloud metadata endpoints, potentially exposing sensitive internal resources. The vulnerability is classified as SSRF with medium severity, depending on the network context of the embedding application. A patch is available to enforce same-origin checks and block private network addresses.

References

Community reviews

Loading reviews…