Bug 2535526 - CVE-2026-63127 goose: RMCP: Token impersonation via missing OAuth resource field validation [epel-all]
Summary: CVE-2026-63127 goose: RMCP: Token impersonation via missing OAuth resource fi...
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: goose
Version: epel10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: RHEL Lightspeed Maint
QA Contact:
URL:
Whiteboard: {"flaws": ["c5e4f491-e66f-4565-b1d8-2...
Depends On:
Blocks: CVE-2026-63127
TreeView+ depends on / blocked
 
Reported: 2026-09-16 16:02 UTC by Samuele Negrini
Modified: 2026-09-16 16:02 UTC (History)
3 users (show)

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


Attachments (Terms of Use)

Description Samuele Negrini 2026-09-16 16:02:01 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.