Bump anyhow and crossbeam-epoch for two advisories - #71
Merged
Conversation
RUSTSEC-2026-0190 reports unsoundness in anyhow's Error::downcast_mut(), fixed in 1.0.103. RUSTSEC-2026-0204 reports an invalid pointer dereference in crossbeam-epoch's fmt::Pointer impl, fixed in 0.9.20 and reached here through the ignore crate. Lock-only change; neither manifest range moves.
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.
Clear two advisories that
cargo denybegan rejecting once the advisory database caught up. Neither manifest range moves, so this is a lock-only change.RUSTSEC-2026-0190reports unsoundness inanyhow'sError::downcast_mut(): affected versions violate borrow rules and produce undefined behaviour when context is added withError::contextand the result is later downcast mutably. Fixed in 1.0.103; the lock moves to 1.0.104.RUSTSEC-2026-0204reports an invalid pointer dereference in thefmt::Pointerimplementation forcrossbeam-epoch'sAtomicandShared. Fixed in 0.9.20. It arrives here transitively through theignorecrate.No changelog entry: dependency bumps are not user-facing.