RUSTSEC-2021-0033: push_cloned can drop uninitialized memory or double free on panic

What to do

1. See which version you have: cargo tree -i stack_dst (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p stack_dst. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example stack_dst = "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

Affected versions of stack_dst used a push_inner function that increased the internal length of the array and then called val.clone().

If the val.clone() call panics, the stack could drop an already dropped element or drop uninitialized memory.

This issue was fixed in 2a4d538 by increasing the length of the array after elements are cloned.

References

• Package: crates.io/crates/stack_dst
• Advisory: rustsec.org/advisories/RUSTSEC-2021-0033.html
• Report: github.com/thepowersgang/stack_dst-rs/issues/5

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

Other advisories for stack_dst

• UnsoundRUSTSEC-2026-0272 · 2026-08-27Panic-safety unsoundness in `Stack::pop`, `Fifo::pop_front` and `Value::replace_stable` (use-after-free / double-free)

Full security history of stack_dst