Skip to content

fix(security): bump lru 0.12 -> 0.18.1 (RUSTSEC-2026-0002) and unblind the deny gate #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
h4x0r wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix(security): bump lru 0.12 -> 0.18.1 (RUSTSEC-2026-0002) and unblind the deny gate #6

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
183104d
fix(security): bump lru 0.12 -> 0.18.1 (RUSTSEC-2026-0002) and unblin…
h4x0r Aug 2, 2026
b753bd7
chore(vet): re-exempt lru/hashbrown and add foldhash for the 0.18.1 bump
h4x0r Aug 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

6 changes: 5 additions & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,11 @@ flate2 = "1"
# adler-32 over EWF section CRCs (the section-checksum format fact). Already in
# the tree via flate2; declared directly so `ewf::sections` can compute it.
adler2 = "2"
lru = "0.12"
# RUSTSEC-2026-0002 (IterMut invalidated the HashMap's shared pointer, violating
# Stacked Borrows) is patched in >= 0.16.3. The requirement states a minor+patch
# floor rather than a bare "0.18" so a resolver can never land on an affected
# 0.16.0-0.16.2 within the same caret range.
lru = "0.18.1"
rayon = "1"
thiserror = "2"
log = "0.4"
Expand Down
23 changes: 16 additions & 7 deletions core/fuzz/Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

29 changes: 17 additions & 12 deletions deny.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,17 +1,22 @@
[advisories]
version = 2
# - RUSTSEC-2025-0056: `adler` — dev-dep via blazehash-core 0.2.4; superseded by adler2.
# (The crossbeam RUSTSEC-2026-0204 vulnerability was fixed by updating to 0.9.20.)
# RUSTSEC-2025-0119 (number_prefix, unmaintained) was FIXED by bumping indicatif
# 0.17 -> 0.18, which drops number_prefix — genuinely resolved, not ignored.
# RUSTSEC-2026-0002 (console IterMut unsoundness) was ALSO genuinely fixed by that
# bump: every committed Cargo.lock (root, forensic/fuzz, core/fuzz) resolves the
# patched console 0.16.4, and `cargo deny --all-features check` passes locally on
# both macOS and the linux target. The ignore below guards a cargo-deny-ACTION CI
# re-resolution artifact: the Docker action surfaces a phantom console 0.15 that is
# absent from every shipped lock and not reproducible with the identical command
# locally. Remove once the action stops re-resolving (or on the next deny-action bump).
ignore = ["RUSTSEC-2025-0056", "RUSTSEC-2026-0002"]

# `unsound` MUST be set explicitly, or unsoundness advisories are silently
# dropped. cargo-deny 0.19.0 defaults `unsound` to "workspace", but builds the
# workspace-member set it compares against ONLY when the *unmaintained* scope is
# "workspace"/"transitive" (src/advisories.rs:77-93). With `unmaintained` at its
# own "all" default that set is empty, so the membership test at line 120 is
# always false and every `informational = "unsound"` advisory hits `continue`
# without ever being reported. "all" takes the unconditional branch (line 111),
# so it does not depend on that set and stays correct if upstream fixes the
# gating. Verified locally against cargo-deny 0.19.0.
unsound = "all"

# Deliberately empty. Every prior entry outlived its cause: RUSTSEC-2026-0002 is
# fixed by lru >= 0.16.3 (see the requirement in Cargo.toml), and `adler`
# (RUSTSEC-2025-0056) has left the graph entirely — cargo-deny now reports both
# as `advisory-not-detected`. Fix the dependency, never re-add the suppression.
ignore = []

[licenses]
version = 2
Expand Down
16 changes: 8 additions & 8 deletions forensic/fuzz/Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 6 additions & 2 deletions supply-chain/config.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -189,6 +189,10 @@ criteria = "safe-to-run"
version = "1.1.9"
criteria = "safe-to-deploy"

[[exemptions.foldhash]]
version = "0.2.0"
criteria = "safe-to-deploy"

[[exemptions.forensic-vfs]]
version = "0.7.0"
criteria = "safe-to-deploy"
Expand Down Expand Up @@ -234,7 +238,7 @@ version = "0.3.3"
criteria = "safe-to-deploy"

[[exemptions.hashbrown]]
version = "0.15.5"
version = "0.17.1"
criteria = "safe-to-deploy"

[[exemptions.indicatif]]
Expand Down Expand Up @@ -270,7 +274,7 @@ version = "0.4.33"
criteria = "safe-to-deploy"

[[exemptions.lru]]
version = "0.12.5"
version = "0.18.1"
criteria = "safe-to-deploy"

[[exemptions.md-5]]
Expand Down
Loading