fix(fuzz): refresh the fuzz lockfile to clear stale RUSTSEC advisories - #475
Merged
Conversation
Dependabot flagged quinn-proto 0.11.14 (GHSA-4w2j-m93h-cj5j, high — remote memory exhaustion via unbounded out-of-order stream reassembly) in `fuzz/Cargo.lock`. The fuzz crate is a SEPARATE cargo workspace with its own lockfile, so none of this session's main-lock bumps reached it — it had drifted several advisories behind (quinn-proto, crossbeam-epoch RUSTSEC-2026-0204, and the now-removed rsa/spin from the jsonwebtoken aws_lc_rs swap). Regenerated the fuzz lock against grob's current Cargo.toml with `cargo update --manifest-path fuzz/Cargo.toml`. quinn-proto -> 0.11.16, crossbeam-epoch -> 0.9.20, and the tree now mirrors the main resolution. `cargo audit -f fuzz/Cargo.lock` exits clean (was 1 vulnerability + warnings). Fuzz binaries are never shipped, but a stale mirror lock is exactly what keeps re-triggering these alerts, so keeping it current is the fix. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Destynova2
enabled auto-merge
July 26, 2026 07:03
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.
What
Dependabot alert #34: quinn-proto 0.11.14 (GHSA-4w2j-m93h-cj5j, high —
remote memory exhaustion via unbounded out-of-order stream reassembly), in
fuzz/Cargo.lock.The
fuzzcrate is a separate cargo workspace with its own lockfile(deliberately, to not interfere with the main workspace). So none of this
session's main-lock security bumps reached it — it had drifted several
advisories behind:
Fix
Regenerated the fuzz lock against grob's current
Cargo.toml:It now mirrors the main resolution. Large diff because the lock was stale, not
because of broad version jumps.
Verification
cargo audit -f fuzz/Cargo.lock— exits clean (was1 vulnerability found+ warnings)cargo metadata --manifest-path fuzz/Cargo.toml --locked— resolvesCargo.lockuntouched; maincargo auditstill cleanFuzz binaries are never shipped, but a stale mirror lockfile is exactly what
keeps re-triggering these alerts, so keeping it current is the actual fix rather
than dismissing the alert.
Note
fuzz/Cargo.lockisn't covered by release-plz or the maincargo update, so itwill drift again. A dedicated Dependabot ecosystem entry for
/fuzz(or foldingit into the existing cargo config) would keep it current automatically — flagging
as a follow-up rather than doing it here.
🤖 Generated with Claude Code