How severe is GHSA-rhfx-m35p-ff5j?

No CVSS score has been assigned to GHSA-rhfx-m35p-ff5j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rhfx-m35p-ff5j?

GHSA-rhfx-m35p-ff5j affects the following packages: lru (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-rhfx-m35p-ff5j?

Update lru to 0.16.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rhfx-m35p-ff5j is resolved across your whole dependency graph.

How do I detect GHSA-rhfx-m35p-ff5j in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lru, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rhfx-m35p-ff5j if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rhfx-m35p-ff5j?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rhfx-m35p-ff5j can be triaged on real exposure rather than presence alone.

Is GHSA-rhfx-m35p-ff5j actively exploited in the wild?

No public exploit code has been indexed for GHSA-rhfx-m35p-ff5j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-rhfx-m35p-ff5j published, and has it been updated?

GHSA-rhfx-m35p-ff5j was published on January 7, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-rhfx-m35p-ff5j — lru

Fix: jeromefroe/lru-rs#224

GHSA-rhfx-m35p-ff5j is a security vulnerability in lru. A fix is available for lru — see the affected versions and patch details below.

`IterMut` violates Stacked Borrows by invalidating internal pointer

Also known asRUSTSEC-2026-0002

Published

Jan 7, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀lru

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Affected versions of this crate contain a soundness issue in the IterMut iterator implementation. The IterMut::next and IterMut::next_back methods 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`lru`	≥ 0.9.0&&< 0.16.3	0.16.3`cargo update -p lru --precise 0.16.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lru, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update lru to 0.16.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rhfx-m35p-ff5j is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rhfx-m35p-ff5j can be triaged on real exposure rather than presence alone.

Tailored to GHSA-rhfx-m35p-ff5j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of this crate contain a soundness issue in the `IterMut` iterator implementation. The `IterMut::next` and `IterMut::next_back` methods 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.

O3 Security · Impact-Aware SCA

Is GHSA-rhfx-m35p-ff5j in your dependencies?

O3 Security finds GHSA-rhfx-m35p-ff5j across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works