Rust advisories / rcu_cell
Vulnerability HighRUSTSEC-2020-0131 · rcu_cell
RUSTSEC-2020-0131: Send/Sync bound needed on T for Send/Sync impl of RcuCell<T>
Short answerA security vulnerability in the rcu_cell crate: Send/Sync bound needed on T for Send/Sync impl of RcuCell<T>. High severity (CVSS 8.1). No fixed version: replace the crate or remove the affected code path.
| Crate | rcu_cell |
|---|---|
| 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-11-14 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36451, GHSA-686h-j8r8-wmfm |
What to do
- Find who pulls it in:
cargo tree -i rcu_cell. - Avoid the affected API, or replace the crate.
Details from the advisory
Affected versions of this crate unconditionally implement Send/Sync for RcuCell<T>. This allows users to send T: !Send to other threads (while T enclosed within RcuCell<T>), and allows users to concurrently access T: !Sync by using the APIs of RcuCell<T> that provide access to &T.
This can result in memory corruption caused by data races.
References
- Package: crates.io/crates/rcu_cell
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0131.html
- Report: github.com/Xudong-Huang/rcu_cell/issues/3
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?