Rust advisories / multiqueue
Vulnerability HighRUSTSEC-2020-0143 · multiqueue
RUSTSEC-2020-0143: Queues allow non-Send types to be sent to other threads, allowing data races
Short answerA security vulnerability in the multiqueue crate: Queues allow non-Send types to be sent to other threads, allowing data races. High severity (CVSS 8.1). No fixed version: replace the crate or remove the affected code path.
| Crate | multiqueue |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Every version. |
| Fixed in | none |
| 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-25 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36463, GHSA-jf43-3v8j-qwwr, GHSA-r2x6-vrxx-jgv4 |
What to do
- Find who pulls it in:
cargo tree -i multiqueue. - Avoid the affected API, or replace the crate.
Details from the advisory
Affected versions of this crate unconditionally implemented Send for types used in queue implementations (InnerSend<RW, T>, InnerRecv<RW, T>, FutInnerSend<RW, T>, FutInnerRecv<RW, T>).
This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior.
References
- Package: crates.io/crates/multiqueue
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0143.html
- Report: github.com/schets/multiqueue/issues/31
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?