Skip to content

CVE-2026-63127 RMCP: Missing Resource Field Validation in OAuth Protected Resource Metadata Discovery

HighCVSS 8.2 EPSS 0.19%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
Proof of concept public · automatable: no · technical impact: partial
Technology
Red Hat

Description

RMCP is an official Rust SDK for the Model Context Protocol. Prior to 2.0.0, the rmcp crate's OAuth implementation in crates/rmcp/src/transport/auth.rs omits the RFC 9728 resource field from ResourceServerMetadata and allows discover_oauth_server_via_resource_metadata to use protected-resource metadata without confirming that the returned resource identifier exactly matches the configured MCP server. A malicious MCP server can publish metadata for a different legitimate MCP resource and its authorization server, causing a victim who connects and completes the authorization flow to obtain a legitimate access token that the client subsequently sends to the malicious server. The attacker can capture the token and impersonate the victim against the legitimate MCP resource within the token's granted scopes. This issue is fixed in version 2.0.0.

Upgrade path

4 packages: 1 fixed, 2 with no fix yet.

PackageAffectedFixed inStatus
redhat/goose(Red Hat enterprise_linux 10) All versions No fix listed No fix yet
redhat/goose(Red Hat enterprise_linux 9) All versions No fix listed No fix yet
crates.io rmcp(crates.io) < 2.0.0 2.0.0 Fixed
modelcontextprotocol rust-sdk = < 2.0.0 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
modelcontextprotocol rust-sdk = < 2.0.0 No fix listed
crates.io rmcp(crates.io) < 2.0.0 2.0.0
redhat/goose(Red Hat:enterprise_linux:10) All versions No fix listed
redhat/goose(Red Hat:enterprise_linux:9) All versions No fix listed

References