This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate rmcp

Dependencies

(28 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.890.1.89up to date
 axum^0.80.8.7up to date
 base64^0.220.22.1up to date
 bytes^11.11.0up to date
 chrono^0.4.380.4.42up to date
 futures^0.30.3.31up to date
 http^11.3.1up to date
 http-body^11.0.1up to date
 http-body-util^0.10.1.3up to date
 oauth2^5.05.0.0up to date
 paste^11.0.15up to date
 pin-project-lite^0.20.2.16up to date
 process-wrap^8.29.0.0out of date
 rand^0.90.9.2up to date
 reqwest^0.120.12.24up to date
 rmcp-macros^0.9.00.9.0up to date
 schemars^1.01.1.0up to date
 serde^1.01.0.228up to date
 serde_json^1.01.0.145up to date
 sse-stream^0.20.2.1up to date
 thiserror^22.0.17up to date
 tokio ⚠️^11.48.0maybe insecure
 tokio-stream^0.10.1.17up to date
 tokio-util^0.70.7.17up to date
 tower-service^0.30.3.3up to date
 tracing^0.10.1.41up to date
 url^2.42.5.7up to date
 uuid^11.18.1up to date

Dev dependencies

(5 total, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.100up to date
 async-trait^0.10.1.89up to date
 schemars^1.01.1.0up to date
 tokio ⚠️^11.48.0maybe insecure
 tracing-subscriber ⚠️^0.30.3.20maybe insecure

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

This was patched in PR #3368 to escape ANSI control characters from user input.