`MsQueue` `push`/`pop` use the wrong orderingsGHSA-rwf4-gx62-rqfw
Fix: crossbeam-rs/crossbeam#98GHSA-rwf4-gx62-rqfw is a remote code execution vulnerability in crossbeam. A fix is available for crossbeam — see the affected versions and patch details below.
Real-World Exposure
crossbeamReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Affected versions of this crate use orderings which are too weak to support this data structure. It is likely this has caused memory corruption in the wild: https://github.com/crossbeam-rs/crossbeam/issues/97#issuecomment-412785919.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | crossbeam | all versions | 0.3.0cargo update -p crossbeam --precise 0.3.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for crossbeam, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update crossbeam to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rwf4-gx62-rqfw is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
Frequently Asked Questions
Is GHSA-rwf4-gx62-rqfw in your dependencies?
Find it across crates.io, including transitive dependencies.