Rust advisories / magnetic
Vulnerability MediumRUSTSEC-2020-0088 · magnetic
RUSTSEC-2020-0088: MPMCConsumer/Producer allows sending non-Send type across threads
Short answerA security vulnerability in the magnetic crate: MPMCConsumer/Producer allows sending non-Send type across threads. Medium severity (CVSS 5.5). Fixed in 2.0.1: update to a fixed version.
| Crate | magnetic |
|---|---|
| Type | Vulnerability (thread-safety) |
| Affected versions | Before 2.0.1. |
| Fixed in | 2.0.1 |
| 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-29 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-35925, GHSA-wv4p-jp67-jr97 |
What to do
- See which version you have:
cargo tree -i magnetic(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p magnetic. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplemagnetic = "2.0.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
Affected versions of this crate unconditionally implemented Sync and Send traits for MPMCConsumer and MPMCProducer types.
This allows users to send types that do not implement Send trait across thread boundaries, which can cause a data race.
The flaw was corrected in the 2.0.1 release by adding T: Send bound to affected Sync/Send trait implementations.
References
- Package: crates.io/crates/magnetic
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0088.html
- Report: github.com/johnshaw/magnetic/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?