fix(deps): bump crossbeam-epoch to 0.9.20 (RUSTSEC-2026-0204)#359
Merged
Conversation
RustSec published RUSTSEC-2026-0204: an invalid pointer dereference in the fmt::Pointer impl for crossbeam-epoch's Atomic and Shared when the underlying pointer is invalid. It reaches us transitively via crossbeam-deque. The fix is a lock-only patch bump to the already-compatible 0.9.20 (no Cargo.toml or code change). cargo-deny's advisories check now passes.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cargo-denystarted failing onRUSTSEC-2026-0204— an invalid pointer dereference in crossbeam-epoch'sfmt::Pointerimpl forAtomic/Shared, reaching us transitively throughcrossbeam-deque. The advisory was published after the last green run, so it reddens the supply-chain check on every PR (and the next main push) org-wide, not just here.Official fix: upgrade to
>=0.9.20. This is a lock-only patch bump (cargo update -p crossbeam-epoch,0.9.18 -> 0.9.20) — noCargo.tomlor code change. Restorescargo-deny(advisories) to green.