Vulnerability CriticalRUSTSEC-2018-0009 · crossbeam
RUSTSEC-2018-0009: MsQueue and SegQueue suffer from double-free
Short answerA security vulnerability in the crossbeam crate: MsQueue and SegQueue suffer from double-free. Critical severity (CVSS 9.8). Fixed in 0.4.1: update to a fixed version.
| Crate | crossbeam |
|---|---|
| Type | Vulnerability |
| Affected versions | From 0.4.0 before 0.4.1. |
| Fixed in | 0.4.1 |
| Severity | Critical, CVSS 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Published | 2018-12-09 |
| Last changed | 2026-07-17 |
| Also known as | CVE-2018-20996, GHSA-c3cw-c387-pj65 |
What to do
- See which version you have:
cargo tree -i crossbeam(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p crossbeam. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplecrossbeam = "0.4.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
Even if an element is popped from a queue, crossbeam would run its destructor inside the epoch-based garbage collector. This is a source of double frees.
The flaw was corrected by wrapping elements inside queues in a ManuallyDrop.
Thanks to @c0gent for reporting the issue.
References
- Package: crates.io/crates/crossbeam
- Advisory: rustsec.org/advisories/RUSTSEC-2018-0009.html
- Report: github.com/crossbeam-rs/crossbeam-epoch/issues/82
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for crossbeam
Up next
Same cratecrossbeam: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?