Rust advisories / late-static
Vulnerability HighRUSTSEC-2020-0102 · late-static
RUSTSEC-2020-0102: LateStatic has incorrect Sync bound
Short answerA security vulnerability in the late-static crate: LateStatic has incorrect Sync bound. High severity (CVSS 7.0). Fixed in 0.4.0: update to a fixed version.
| Crate | late-static |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Before 0.4.0. |
| Fixed in | 0.4.0 |
| Severity | High, CVSS 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| Published | 2020-11-10 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36209, GHSA-wr55-mf5c-hhwm |
What to do
- See which version you have:
cargo tree -i late-static(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p late-static. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplelate-static = "0.4.0") 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
Affected versions of this crate implemented Sync for LateStatic with T: Send, so that it is possible to create a data race to a type T: Send + !Sync (e.g. Cell<T>).
This can result in a memory corruption or other kinds of undefined behavior.
The flaw was corrected in commit 11f396c by replacing the T: Send bound to T: Sync bound in the Sync impl for LateStatic<T>.
References
- Package: crates.io/crates/late-static
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0102.html
- Report: github.com/Richard-W/late-static/issues/1
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?