Rust advisories / lazy-init
Vulnerability MediumRUSTSEC-2021-0004 · lazy-init
RUSTSEC-2021-0004: Missing Send bound for Lazy
Short answerA security vulnerability in the lazy-init crate: Missing Send bound for Lazy. Medium severity (CVSS 5.3). Fixed in 0.4.1: update to a fixed version.
| Crate | lazy-init |
|---|---|
| Type | Vulnerability (memory-corruption) |
| Affected versions | Before 0.4.1. |
| Fixed in | 0.4.1 |
| Severity | Medium, CVSS 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| Published | 2021-01-17 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2021-25901, GHSA-w47j-hqpf-qw9w |
What to do
- See which version you have:
cargo tree -i lazy-init(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p lazy-init. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplelazy-init = "0.4.1") 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
All current versions of this crate allow causing data races in safe code.
The flaw will be fixed in the next release.
References
- Package: crates.io/crates/lazy-init
- Advisory: rustsec.org/advisories/RUSTSEC-2021-0004.html
- Report: github.com/khuey/lazy-init/issues/9
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?