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 tokio-tungstenite


(10 total, 5 outdated, 2 possibly insecure)

 futures-util^ to date
 log^ to date
 native-tls^ to date
 rustls ⚠️^ of date
 rustls-native-certs^ of date
 tokio ⚠️^ insecure
 tokio-native-tls^ to date
 tokio-rustls^ of date
 tungstenite^ of date
 webpki-roots^ of date

Dev dependencies

(5 total, 2 outdated)

 env_logger^ of date
 futures-channel^ to date
 hyper^ of date
 tokio^ to date
 url^ to date

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption


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.


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

let mut opts = ServerOptions::new();

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input


If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.