Rust advisories / try-mutex
Vulnerability MediumRUSTSEC-2020-0087 · try-mutex
RUSTSEC-2020-0087: TryMutex<T> allows sending non-Send type across threads
Short answerA security vulnerability in the try-mutex crate: TryMutex<T> allows sending non-Send type across threads. Medium severity (CVSS 5.5). Fixed in 0.3.0: update to a fixed version.
| Crate | try-mutex |
|---|---|
| Type | Vulnerability (thread-safety) |
| Affected versions | Before 0.3.0. |
| Fixed in | 0.3.0 |
| Severity | Medium, CVSS 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| Published | 2020-11-17 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-35924, GHSA-64j8-7gp2-xjx5 |
What to do
- See which version you have:
cargo tree -i try-mutex(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p try-mutex. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampletry-mutex = "0.3.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 unconditionally implemented Sync trait for TryMutex<T> type.
This allows users to put non-Send T type in TryMutex and send it to another thread, which can cause a data race.
The flaw was corrected in the 0.3.0 release by adding T: Send bound for the Sync trait implementation.
References
- Package: crates.io/crates/try-mutex
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0087.html
- Report: github.com/mpdn/try-mutex/issues/2
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?