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 wiggle

Dependencies

(8 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.931.0.100up to date
 async-trait^0.1.710.1.89up to date
 bitflags^2.02.10.0up to date
 thiserror^2.0.122.0.17up to date
 tracing^0.1.260.1.43up to date
 wasmtime ⚠️^33.0.239.0.1out of date
 wiggle-macro=33.0.239.0.1out of date
 witx^0.9.10.9.1up to date

Dev dependencies

(3 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 proptest^1.0.01.9.0up to date
 tokio ⚠️^11.48.0maybe insecure
 wasmtime ⚠️^33.0.239.0.1out of date

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);

wasmtime: Unsound API access to a WebAssembly shared linear memory

RUSTSEC-2025-0118

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hc7m-r6v8-hg9q For more information see the GitHub-hosted security advisory.