fix(deps): bump crossbeam-epoch to 0.9.20 (RUSTSEC-2026-0204) - #50
Open
saagpatel wants to merge 1 commit into
Open
fix(deps): bump crossbeam-epoch to 0.9.20 (RUSTSEC-2026-0204)#50saagpatel wants to merge 1 commit into
saagpatel wants to merge 1 commit into
Conversation
RUSTSEC-2026-0204: invalid pointer dereference in the fmt::Pointer/Display impl for Atomic/Shared when the pointer is null/invalid. Transitive via moka; low practical severity (no CVSS; only fires if code Display-formats a crossbeam pointer). RustSec-only, so Dependabot never alerts or PRs it. Surgical bump; cargo check passes.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
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.lockcurrently resolvescrossbeam-epochto 0.9.18, which is affected byRUSTSEC-2026-0204. This bumps it to 0.9.20.
Lockfile only — no manifest change, no API surface touched, and
crossbeam-epochis a transitive dependency, so the bump is within the range already declared
upstream of it.
cargo auditstops reporting the advisory after this change.