RUSTSEC-2021-0032: Deserializing an array can drop uninitialized memory on panic

What to do

1. See which version you have: cargo tree -i byte_struct (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p byte_struct. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example byte_struct = "0.6.1") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

The read_bytes_default_le function for [T; n] arrays, used to deserialize arrays of T from bytes created a [T; n] array with std::mem::uninitialized and then called T's deserialization method.

If T's deserialization method panicked, the uninitialized memory could drop invalid objects.

This flaw was corrected in a535678 by removing the unsafe block and using a .map function to deserialize each element of the array instead.

References

• Package: crates.io/crates/byte_struct
• Advisory: rustsec.org/advisories/RUSTSEC-2021-0032.html
• Report: github.com/wwylele/byte-struct-rs/issues/1

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.