CVE-2026-63127

Published: Set 16, 2026 Last Modified: Set 16, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 8,2
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: required
Scope: changed
Confidentiality: high
Integrity: low
Availability: none

Description

AI Translation Available

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.

345

Insufficient Verification of Data Authenticity

Draft
Common Consequences
Security Scopes Affected:
Integrity Other
Potential Impacts:
Varies By Context Unexpected State
Applicable Platforms
Technologies: ICS/OT
View CWE Details
https://github.com/modelcontextprotocol/rust-sdk/security/advisories/GHSA-33f5-…
https://github.com/modelcontextprotocol/rust-sdk/commit/c1a8b29ff2cc45e7820b900…
https://github.com/modelcontextprotocol/rust-sdk/pull/937
https://github.com/modelcontextprotocol/rust-sdk/releases/tag/rmcp-v2.0.0
https://github.com/modelcontextprotocol/rust-sdk/security/advisories/GHSA-33f5-…