rmcp
Affected
- introduced
0.2.0, fixed3.9.0(semver)
Fixed versions
3.9.0
Fix
- Fixed version
3.9.0cargo update -p rmcp --precise 3.9.0
Advisory
Also known as: GHSA-c9f9-cp8h-jcj5
Unbounded response body buffering in Streamable HTTP clients
Before 3.9.0, the built-in Streamable HTTP clients in rmcp read non-streaming
HTTP response bodies into memory with no size limit. Both the reqwest client
(transport-streamable-http-client-reqwest) and the Unix socket client
(transport-streamable-http-client-unix-socket) were affected:
application/json responses to POST requests were read in full before parsing.A malicious or compromised MCP server can answer with a body that never ends,
for example a chunked application/json response that streams whitespace. The
client buffers it until the process runs out of memory. This works duringinitialize, before any authentication. On desktop or agent hosts, this
terminates the whole host application.
Server-sent event streams are not affected. Each event is already capped bymax_sse_event_size, and events are not accumulated.
The flaw was corrected in 3.9.0. Successful JSON bodies are limited to 16 MiB
and non-success bodies to 64 KiB. Bytes are counted while streaming, after
decompression. An oversized Content-Length is rejected before the body is
read, and an oversized body is rejected withStreamableHttpError::ResponseBodyTooLarge instead of being truncated.
If you cannot upgrade, use a custom StreamableHttpClient that enforces a
response body limit, or connect only to trusted MCP servers.
Medium Basis: CVSS v3 score 6.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
0.2.0, fixed 3.9.0 (semver)3.9.0
3.9.0cargo update -p rmcp --precise 3.9.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0