Skip to content

fix(deps): bump crossbeam-epoch to 0.9.20 (RUSTSEC-2026-0204) - #50

Open
saagpatel wants to merge 1 commit into
devwhodevs:mainfrom
saagpatel:fix/crossbeam-epoch-rustsec-2026-0204
Open

fix(deps): bump crossbeam-epoch to 0.9.20 (RUSTSEC-2026-0204)#50
saagpatel wants to merge 1 commit into
devwhodevs:mainfrom
saagpatel:fix/crossbeam-epoch-rustsec-2026-0204

Conversation

@saagpatel

Copy link
Copy Markdown

Cargo.lock currently resolves crossbeam-epoch to 0.9.18, which is affected by
RUSTSEC-2026-0204. This bumps it to 0.9.20.

Lockfile only — no manifest change, no API surface touched, and crossbeam-epoch
is a transitive dependency, so the bump is within the range already declared
upstream of it.

cargo audit stops reporting the advisory after this change.

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.
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant