PatchTheCVECVE-2020-25573: An issue was discovered in the linked-hash-map crate before 0.5.3 for Rust
CVE-2020-25573 is a critical-severity flaw (CVSS 9.8) affecting linked-hash-map. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Critical severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.8% (top 21%) |
| CISA exploited list | No |
| Weakness | CWE-824 |
| Published | 2020-09-14 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2020-25573?
linked-hash-map: upgrade to 0.5.3. Exact commands for each OS are on this page.
Is CVE-2020-25573 being exploited?
CVE-2020-25573 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2020-25573 affect?
CVE-2020-25573 affects linked-hash-map. Severity is critical (CVSS 9.8). 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.
How urgent is CVE-2020-25573?
Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action