fix(deps): update rust crate lru to 0.16.0 [security] #2106
+6
−6
Conversation
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.
This PR contains the following updates:
0.13.0→0.16.0GitHub Vulnerability Alerts
GHSA-rhfx-m35p-ff5j
Affected versions of this crate contain a soundness issue in the
IterMutiterator implementation. TheIterMut::nextandIterMut::next_backmethods temporarily create an exclusive reference to the key when dereferencing the internal node pointer.This invalidates the shared pointer held by the internal
HashMap, violating Stacked Borrows rules.IterMutviolates Stacked Borrows by invalidating internal pointerGHSA-rhfx-m35p-ff5j / RUSTSEC-2026-0002
More information
Details
Affected versions of this crate contain a soundness issue in the
IterMutiterator implementation. TheIterMut::nextandIterMut::next_backmethods temporarily create an exclusive reference to the key when dereferencing the internal node pointer.This invalidates the shared pointer held by the internal
HashMap, violating Stacked Borrows rules.Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:UReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
IterMutviolates Stacked Borrows by invalidating internal pointerGHSA-rhfx-m35p-ff5j / RUSTSEC-2026-0002
More information
Details
Affected versions of this crate contain a soundness issue in the
IterMutiterator implementation. The
IterMut::nextandIterMut::next_backmethods temporarily create an exclusive reference to the key when
dereferencing the internal node pointer.
This invalidates the shared pointer held by the internal
HashMap,violating Stacked Borrows rules.
Severity
Unknown
References
This data is provided by OSV and the Rust Advisory Database (CC0 1.0).
Release Notes
jeromefroe/lru-rs (lru)
v0.16.3Compare Source
IterMut.v0.16.2Compare Source
v0.16.1Compare Source
Clonefor unbounded cache.v0.16.0Compare Source
Clonefor caches with custom hashers.v0.15.0Compare Source
promoteanddemoteto indicate whether key was found.v0.14.0Compare Source
NonZeroUsize::MAXinstead ofunwrap(), and update MSRV to 1.70.0.Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.
This change is