How severe is GHSA-qqmc-hwqp-8g2w?

No CVSS score has been assigned to GHSA-qqmc-hwqp-8g2w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qqmc-hwqp-8g2w?

GHSA-qqmc-hwqp-8g2w affects the following packages: lru (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-qqmc-hwqp-8g2w?

Update lru to 0.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qqmc-hwqp-8g2w is resolved across your whole dependency graph.

How do I detect GHSA-qqmc-hwqp-8g2w 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-qqmc-hwqp-8g2w if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-qqmc-hwqp-8g2w actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-qqmc-hwqp-8g2w, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-qqmc-hwqp-8g2w?

GHSA-qqmc-hwqp-8g2w has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 69th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-qqmc-hwqp-8g2w?

GHSA-qqmc-hwqp-8g2w is classified as Use After Free (CWE-416). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qqmc-hwqp-8g2w published, and has it been updated?

GHSA-qqmc-hwqp-8g2w was published on June 17, 2022 and was last updated on November 8, 2023. 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

Use after free in lru crateGHSA-qqmc-hwqp-8g2w

GHSA-qqmc-hwqp-8g2w is a Use After Free vulnerability in lru. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for lru — see the affected versions and patch details below.

Also known asCVE-2021-45720 GHSA-v362-2895-h9r2RUSTSEC-2021-0130

Published

Jun 17, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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

Lru crate has use after free vulnerability.

Lru crate has two functions for getting an iterator. Both iterators give references to key and value. Calling specific functions, like pop(), will remove and free the value, and but it's still possible to access the reference of value which is already dropped causing use after free.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`lru`	all versions	0.7.1`cargo update -p lru --precise 0.7.1`

Affected Products

1 product · 1 configurations

Application

lrulru_project

< 0.7.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An issue was discovered in the lru crate before 0.7.1 for Rust. The iter…

rustsec.orgNVDJan 2022

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.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qqmc-hwqp-8g2w is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

Lru crate has use after free vulnerability. Lru crate has two functions for getting an iterator. Both iterators give references to key and value. Calling specific functions, like pop(), will remove and free the value, and but it's still possible to access the reference of value which is already dropped causing use after free.