Rust advisories / crossbeam-epoch
VulnerabilityRUSTSEC-2026-0204 · crossbeam-epoch
RUSTSEC-2026-0204: Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalid
Short answerA security vulnerability in the crossbeam-epoch crate: Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalid. No severity score was published. Fixed in 0.9.20: update to a fixed version.
| Crate | crossbeam-epoch |
|---|---|
| Type | Vulnerability |
| Affected versions | From 0.9.0 before 0.9.20. |
| Fixed in | 0.9.20 |
| Severity | not scored |
| Published | 2026-07-06 |
| Last changed | 2026-07-06 |
| Also known as | none |
What to do
- See which version you have:
cargo tree -i crossbeam-epoch(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p crossbeam-epoch. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplecrossbeam-epoch = "0.9.20") 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 fmt::Display dereference the underlying pointer. This causes a invalid pointer dereference e.g., when a pointer created with Atomic::null or Shared::null. fmt::Debug impls and pre-0.9 fmt::Display impls, which do not dereference pointers, are not affected by this issue.
References
- Package: crates.io/crates/crossbeam-epoch
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0204.html
- Web: github.com/crossbeam-rs/crossbeam/pull/1276
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
Same cratecrossbeam-epoch: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?