RMCP: DNS rebinding vulnerability in rmcp Streamable HTTP server transport
modelcontextprotocol rust-sdk
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| rmcp crates.io |
|
|
| dynoxide-rs crates.io |
|
|
| dynoxide |
modelcontextprotocol rust-sdk
| Product | Affected | Fixed in |
|---|---|---|
| rmcp crates.io |
|
|
| dynoxide-rs crates.io |
|
|
| dynoxide |
|
|
RMCP is an official Rust SDK for the Model Context Protocol. Prior to version 1.4.0, the rmcp crate's Streamable HTTP server transport (crates/rmcp/src/transport/streamable_http_server/) did not validate the incoming Host header. This allowed a malicious public website, via a DNS rebinding attack, to send authenticated requests to an MCP server running on the victim's loopback or private-network interface. This vulnerability is fixed in 1.4.0.
From the CVE record · GitHub_M
Before version 1.4.0, rmcp’s Streamable HTTP server transport did not validate the incoming Host header. If a victim visits a malicious public website, an attacker can use DNS rebinding to send authenticated requests to an MCP server on the victim’s loopback or private network.
Teams using rmcp before 1.4.0, dynoxide-rs 0.9.3 through 0.9.12, or npm dynoxide 0.9.3 through 0.9.12 should check their dependencies.