Unsound MediumRUSTSEC-2023-0031 · spin
RUSTSEC-2023-0031: Initialisation failure in `Once::try_call_once` can lead to undefined behaviour for other initialisers
Short answerspin has an API that can cause undefined behaviour from safe code: Initialisation failure in `Once::try_call_once` can lead to undefined behaviour for other initialisers. Fixed in 0.9.8.
| Crate | spin |
|---|---|
| Type | Unsound |
| Affected versions | From 0.9.3 before 0.9.8. |
| Fixed in | 0.9.8 |
| Severity | Medium (GitHub rating) |
| Published | 2023-03-31 |
| Last changed | 2023-11-08 |
| Also known as | GHSA-2qv5-7mw5-j3cg |
What to do
- See which version you have:
cargo tree -i spin(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p spin. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplespin = "0.9.8") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Once::try_call_once is unsound if invoked more than once concurrently and any call fails to initialise successfully.
References
- Package: crates.io/crates/spin
- Advisory: rustsec.org/advisories/RUSTSEC-2023-0031.html
- Report: github.com/mvdnes/spin-rs/issues/148
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 spin
Up next
Same cratespin: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?