Skip to content
OpenAdvisories
High · 8.2 CVE-2026-63127 EUVD-2026-80824GHSA-33f5-2c5q-wgwj

RMCP: Missing Resource Field Validation in OAuth Protected Resource Metadata Discovery

Published Sep 16, 2026 · Updated Sep 16, 2026 · Assigned by GitHub_M

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.

Affected products

VendorProductAffectedFixed
modelcontextprotocol rust-sdk < 2.0.0 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
RHEL 10 goose 1.45.0-1.el10_2 RHSA-2026:80765
RHEL 9 goose 1.45.0-1.el9_8 RHSA-2026:80764
ReleasePackageFixed inAdvisory
openSUSE Tumbleweed openai-codex 0.155.1-1.1 openSUSE-SU-2026:11849-1

Affected packages

EcosystemPackageAffectedFixedRecord
crates.io rmcp < 2.0.0 2.0.0 GHSA-33f5-2c5q-wgwj

Advisories 4

References