Bug 2535503 (CVE-2026-63127) - CVE-2026-63127 rmcp: RMCP: Token impersonation via missing OAuth resource field validation
Summary: CVE-2026-63127 rmcp: RMCP: Token impersonation via missing OAuth resource fie...
Keywords:
Status: NEW
Alias: CVE-2026-63127
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2535525 2535526
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-16 15:05 UTC by OSIDB Bzimport
Modified: 2026-09-16 16:02 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-16 15:05:10 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.