fix: bump crossbeam-epoch to 0.9.20 for RUSTSEC-2026-0204#291
Merged
Navi Bot (project-navi-bot) merged 1 commit intoJul 14, 2026
Merged
Conversation
crossbeam-epoch 0.9.18 (transitive: rayon -> rayon-core -> crossbeam-deque) carries RUSTSEC-2026-0204 (invalid pointer dereference in the fmt::Pointer impl for Atomic/Shared). Lockfile-only patch bump in both the workspace lock and fuzz/Cargo.lock; no manifest changes. Clears the cargo-deny advisories failure on the scheduled audit workflow and on PR CI. Signed-off-by: Nelson Spence <nelson@projectnavi.ai>
Nelson Spence (Fieldnote-Echo)
requested review from
Navi Bot (project-navi-bot) and
Todd Baur (toadkicker)
as code owners
July 14, 2026 00:20
Code Review by QodoNo Changes in PRQodo reviewed your PR and found no changes in the code |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Member
Author
project-navi-bot
approved these changes
Jul 14, 2026
Navi Bot (project-navi-bot)
deleted the
fix/rustsec-2026-0204-crossbeam-epoch
branch
July 14, 2026 00:51
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
2 participants
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.
Summary
crossbeam-epoch 0.9.18(transitive dep:rayon→rayon-core→crossbeam-deque) carries RUSTSEC-2026-0204 — invalid pointer dereference in thefmt::Pointerimpl forAtomic/Shared. This is what's failing thecargo-deny advisoriesjob on the scheduledauditworkflow (main) and on PR CI for #289/#290.Lockfile-only patch bump to 0.9.20 in both the workspace
Cargo.lockandfuzz/Cargo.lock(same vulnerable pin there; fuzz smoke jobs exercise it). No manifest changes.Note:
cargo deny check advisoriesalso emits aadvisory-not-detectedwarning for theRUSTSEC-2025-0141(bincode-unmaintained) ignore — bincode 1.3.3 is still in the graph viahnsw_rs(dev-only beir-bench), but current cargo-deny doesn't flag transitive unmaintained advisories. Left the ignore in place deliberately: it's harmless as a warning, and removing it would fail CI if the pinned cargo-deny-action version still detects the advisory.Test plan
cargo deny check advisories→advisories oklocallycargo build --lockedcargo test(core: 256 passed) +cargo test -p ordvec-manifest(70 passed)