RUSTSEC-2022-0054: wee_alloc is Unmaintained

What to do

1. Look for a maintained fork or alternative crate.
2. If you cannot move yet, acknowledge it in your audit config so CI stays green while you plan: add "RUSTSEC-2022-0054" to ignore in .cargo/audit.toml or deny.toml, with a comment saying why.
3. Find who pulls it in: cargo tree -i wee_alloc.

Details from the advisory

Two of the maintainers have indicated that the crate may not be maintained.

The crate has open issues including memory leaks and may not be suitable for production use.

It may be best to switch to the default Rust standard allocator on wasm32 targets.

Last release seems to have been three years ago.

Possible Alternative(s)

The below list has not been vetted in any way and may or may not contain alternatives;

• Rust standard default allocator on wasm32-target

Honorable Mention(s)

The below may serve to educate on potential future alternatives:

• lol_alloc

References

• Package: crates.io/crates/wee_alloc
• Advisory: rustsec.org/advisories/RUSTSEC-2022-0054.html
• Report: github.com/rustwasm/wee_alloc/issues/107
• Web: www.reddit.com/r/rust/comments/x1cle0/dont_use_wee_alloc_in_production_code_targeting/
• Report: github.com/rustwasm/wee_alloc/issues/85
• Report: github.com/rustwasm/wee_alloc/issues/106

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