fix(deny): ignore RUSTSEC-2026-0253 - #630
Closed
iamquang95 wants to merge 1 commit into
Closed
Conversation
Collaborator
Author
|
Close because of #636 |
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.
Ignore this
inforustsec: https://rustsec.org/advisories/RUSTSEC-2026-0253.htmlcargo deny checkfails on RUSTSEC-2026-0253 (lru 0.16.4, unsound):LruCache::pop()frees the node before dropping the key, so a panicking keyDropskipsdetach()and leaves a dangling pointer.Can't be fixed by upgrading or narrowing features:
lruis a non-optional dep ofalloy-providerwith ungated call sites,alloy-provideris load-bearing (crates/eth1wrap/src/lib.rs:107issues the ERC-1271eth_callbehind operator-signature verification), and every publishedalloy-providerthrough 2.3.0 pinslru = "^0.16"while the fix is only in>= 0.18.2— so nocargo update, noalloy2.x bump, no[patch.crates-io].Not reachable either: only a panicking key
Dropskips the detach (the value is moved out, never dropped there), and alloy keys its caches onBlockNumber(u64) andB256, neither of which implementsDrop.