Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀
🦀 crates.io
Not in CISA KEV
CRITICAL severity

Access of Uninitialized Pointer in linked-hash-mapGHSA-r43h-gmrm-h5c9

CRITICALFix: contain-rs/linked-hash-map#100

GHSA-r43h-gmrm-h5c9 is a critical-severity (CVSS 9.8) CWE-824 vulnerability in linked-hash-map. 1 public exploit reference exists, so weaponization risk is real. A fix is available for linked-hash-map — see the affected versions and patch details below.

Also known asCVE-2020-25573RUSTSEC-2020-0026
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk
0.10%0.83%1.56%2.29%0.6%1.8%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-r43h-gmrm-h5c9 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🦀linked-hash-map

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

An issue was discovered in the linked-hash-map crate before 0.5.3 for Rust. It creates an uninitialized NonNull pointer, which violates a non-null constraint.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iolinked-hash-mapall versions0.5.3cargo update -p linked-hash-map --precise 0.5.3

Affected Products

1 product · 1 configurations
Application
linked-hash-maplinked-hash-map_project
< 0.5.3
range
Exploits & PoCs
1

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 linked-hash-map crate before 0.5.3 for Ru…

github.comNVDSep 2020

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update linked-hash-map to 0.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r43h-gmrm-h5c9 is resolved across your whole dependency graph.

  3. 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.

Frequently Asked Questions

An issue was discovered in the linked-hash-map crate before 0.5.3 for Rust. It creates an uninitialized NonNull pointer, which violates a non-null constraint.
O3 Security · Impact-Aware SCA

Is GHSA-r43h-gmrm-h5c9 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works
Access of Uninitialized Pointer in linked-hash-map