Rust advisories / tiny_future
Vulnerability HighRUSTSEC-2020-0118 · tiny_future
RUSTSEC-2020-0118: Future<T> lacks bounds on Send and Sync.
Short answerA security vulnerability in the tiny_future crate: Future<T> lacks bounds on Send and Sync.. High severity (CVSS 8.1). Fixed in 0.4.0: update to a fixed version.
| Crate | tiny_future |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Before 0.4.0. |
| Fixed in | 0.4.0 |
| Severity | High, CVSS 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Published | 2020-12-08 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36438, GHSA-fg42-vwxx-xx5j, GHSA-m296-j53x-xv95 |
What to do
- See which version you have:
cargo tree -i tiny_future(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p tiny_future. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampletiny_future = "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
tiny_future contains a light-weight implementation of Futures. The Future type it has lacked bound on its Send and Sync traits.
This allows for a bug where non-thread safe types such as Cell can be used in Futures and cause data races in concurrent programs.
The flaw was corrected in commit c791919 by adding trait bounds to Future's Send and Sync.
References
- Package: crates.io/crates/tiny_future
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0118.html
- Report: github.com/KizzyCode/tiny_future/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?