CVE-2026-63127: modelcontextprotocol rust-sdk · Insufficient Verification of Data Authenticity
Affects modelcontextprotocol rust-sdkSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 2.0.0 soon.
Data as of 31 Oct 2026, 08:20 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.0.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade rust-sdk and github/modelcontextprotocol/rust-sdk to 2.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| modelcontextprotocolrust-sdk | Affected
| Fixed in
|
crates.iogithub/modelcontextprotocol/rust-sdkpkg:cargo/github/modelcontextprotocol/rust-sdkOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to version 2.0.0 or later of the modelcontextprotocol rust-sdk, where this vulnerability is fixed. No other mitigation is indicated or required according to the available data.
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.
References
- github.com/modelcontextprotocol/rust-sdk/security/advisories/GHSA-33f5-2c5q-wgwj (opens in a new tab)
- github.com/modelcontextprotocol/rust-sdk/pull/937 (opens in a new tab)
- github.com/modelcontextprotocol/rust-sdk/commit/c1a8b29ff2cc45e7820b900dae42cbb4958089ec (opens in a new tab)
- github.com/modelcontextprotocol/rust-sdk/releases/tag/rmcp-v2.0.0 (opens in a new tab)