Deps.rs

wasmer-wasix 0.18.3

[![dependency status](https://deps.rs/crate/wasmer-wasix/0.18.3/status.svg)](https://deps.rs/crate/wasmer-wasix/0.18.3)

This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate wasmer-wasix

Dependencies

(70 total, 32 outdated, 1 insecure)

CrateRequiredLatestStatus
 anyhow^1.0.661.0.104up to date
 async-trait^0.10.1.92up to date
 base64^0.210.23.1out of date
 bincode^1.33.0.0out of date
 blake3^1.01.8.7up to date
 bytecheck^0.6.80.8.3out of date
 bytes^11.12.1up to date
 cfg-if^1.01.0.5up to date
 chrono^0.4.310.4.45up to date
 cooked-waker^55.0.0up to date
 dashmap^5.4.06.2.1out of date
 derivative^22.2.0up to date
 futures^0.30.3.34up to date
 getrandom^0.20.4.3out of date
 heapless^0.7.160.9.3out of date
 hex^0.40.4.3up to date
 http^0.2.81.5.0out of date
 hyper^0.141.11.1out of date
 js-sys^0.3.640.3.105up to date
 lazy_static^1.41.5.0up to date
 libc^0.20.2.189up to date
 linked_hash_set^0.10.1.6up to date
 lz4_flex^0.110.14.0out of date
 num_enum^0.5.70.7.6out of date
 once_cell^1.17.01.21.4up to date
 petgraph^0.6.30.8.3out of date
 pin-project^1.0.121.1.13up to date
 rand^0.80.10.3out of date
 rayon^1.7.01.12.0up to date
 reqwest^0.110.13.5out of date
 rkyv ⚠️^0.7.400.8.18insecure
 rusty_pool^0.7.01.0.0out of date
 semver^1.0.171.0.28up to date
 serde^1.01.0.229up to date
 serde_cbor^0.11.20.11.2up to date
 serde_derive^11.0.229up to date
 serde_json^11.0.151up to date
 serde_yaml^0.90.9.34+deprecatedup to date
 sha2^0.100.11.0out of date
 shared-buffer^0.1.40.1.4up to date
 tempfile^3.6.03.27.0up to date
 term_size^0.30.3.2up to date
 termios^0.30.3.3up to date
 thiserror^12.0.20out of date
 tokio^11.53.1up to date
 tokio-stream^0.10.1.19up to date
 tower^0.4.130.5.3out of date
 tower-http^0.4.00.7.1out of date
 tracing^0.1.370.1.44up to date
 typetag^0.10.2.23out of date
 url^2.3.12.5.8up to date
 urlencoding^22.1.3up to date
 virtual-fs^0.11.20.704.2out of date
 virtual-mio^0.3.10.704.2out of date
 virtual-net^0.6.30.704.2out of date
 waker-fn^1.11.2.0up to date
 wasm-bindgen^0.2.870.2.128up to date
 wasm-bindgen-futures^0.4.370.4.78up to date
 wasmer=4.2.87.4.2out of date
 wasmer-emscripten=4.2.84.4.0out of date
 wasmer-journal^0.1.00.704.2out of date
 wasmer-types=4.2.87.4.2out of date
 wasmer-wasix-types^0.18.30.704.2out of date
 wcgi^0.1.20.3.0out of date
 wcgi-host^0.1.20.3.0out of date
 web-sys^0.3.640.3.105up to date
 webc^5.8.012.0.1out of date
 weezl^0.10.2.1out of date
 winapi^0.30.3.9up to date
 xxhash-rust^0.8.80.8.18up to date

Dev dependencies

(7 total, 1 outdated)

CrateRequiredLatestStatus
 pretty_assertions^1.3.01.4.1up to date
 tokio^11.53.1up to date
 tracing-subscriber^0.30.3.23up to date
 tracing-test^0.2.40.2.6up to date
 tracing-wasm^0.20.2.1up to date
 wasm-bindgen-test^0.3.00.3.78up to date
 wasmer=4.2.87.4.2out of date

Security Vulnerabilities

rkyv: Insufficient archive validation can cause out-of-bounds reads in archives containing Rc/Arc

RUSTSEC-2026-0235

Shared pointer validation keyed already-validated pointees by their address and type, but did not include pointer metadata. For unsized pointees, an archive could therefore contain multiple Rc, Arc, or weak pointers that shared a data address but used different metadata, such as different slice lengths.

Once the first pointer had been validated, later pointers to the same address skipped pointee validation. The safe checked rkyv::access API could consequently return a slice with a forged length, allowing safe indexing to read out of bounds. The same validation bypass was reachable through checked deserialization with rkyv::from_bytes.

Version 0.8.17 includes pointer metadata in shared pointer validation and rejects conflicting metadata. The 0.7 series is also affected but is no longer supported by upstream. Users who process untrusted archives should upgrade to 0.8.17 or later.