RUSTSEC-2023-0058: Exposes reference to non-Sync data to an arbitrary thread

What to do

1. See which version you have: cargo tree -i inventory (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p inventory. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example inventory = "0.2.0") 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 do not enforce a Sync bound on the type of caller-provided value held in the plugin registry. References to these values are made accessible to arbitrary threads other than the one that constructed them.

A caller could use this flaw to submit thread-unsafe data into inventory, then access it as a reference simultaneously from multiple threads.

The flaw was corrected by enforcing that data submitted by the caller into inventory is Sync.

References

• Package: crates.io/crates/inventory
• Advisory: rustsec.org/advisories/RUSTSEC-2023-0058.html
• Web: github.com/dtolnay/inventory/pull/42

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 inventory

• UnsoundRUSTSEC-2023-0057 · 2023-09-10Fails to prohibit standard library access prior to initialization of Rust standard library runtime

Full security history of inventory