PatchTheCVECVE-2019-25010: An issue was discovered in the failure crate through 2019-11-13 for Rust
CVE-2019-25010 is a critical-severity flaw (CVSS 9.8) affecting failure. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
An issue was discovered in the failure crate through 2019-11-13 for Rust. Type confusion can occur when __private_get_type_id__ is overridden.
Why this priority
- Critical severity
- 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.5% (top 25%) |
| CISA exploited list | No |
| Weakness | CWE-843 |
| Published | 2020-12-31 |
| 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-2019-25010?
failure: upgrade to newer than 0.1.5. Exact commands for each OS are on this page.
Is CVE-2019-25010 being exploited?
CVE-2019-25010 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-2019-25010 affect?
CVE-2019-25010 affects failure. Severity is critical (CVSS 9.8). An issue was discovered in the failure crate through 2019-11-13 for Rust. Type confusion can occur when __private_get_type_id__ is overridden.
How urgent is CVE-2019-25010?
Priority 58/100. Critical severity; Remotely exploitable, no login, no user action
Related CVEs
- CVE-2020-25575 CRITICAL 9.8 UPGRADE An issue was discovered in the failure crate through 0.1.5 for Rust