How severe is CVE-2019-25010?

CVE-2019-25010 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2019-25010 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (72nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-25010?

CVE-2019-25010 affects Failure Project Failure. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2019-25010?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2019-25010 published?

CVE-2019-25010 was published on 2020-12-31 and last updated on 2026-06-17.

CVE-2019-25010

CVE-2019-25010 is a critical-severity vulnerability in Failure Project Failure with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-843.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 1% (72nd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-843
Affected product: Failure Project Failure
Published: 2020-12-31
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2019-25010?: 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 severe is CVE-2019-25010?: CVE-2019-25010 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2019-25010 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (72nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-25010?: CVE-2019-25010 affects Failure Project Failure. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-25010?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2019-25010 published?: CVE-2019-25010 was published on 2020-12-31 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:failure_project:failure:*:*:*:*:*:rust:*:*

More vulnerabilities in Failure Project Failure

CVE-2020-25575 — Critical (CVSS 9.8): An issue was discovered in the failure crate through 0.1.5 for Rust. It may introduce "compatibility hazards" in some…

All CVEs affecting Failure Project Failure →

Other CWE-843 vulnerabilities

CVE-2021-33970 — Critical (CVSS 10.0): Buffer Overflow vulnerability in Qihoo 360 Chrome v13.0.2170.0 allows attacker to escalate priveleges.
CVE-2010-2299 — Critical (CVSS 10.0): The Clipboard::DispatchObject function in app/clipboard/clipboard.cc in Google Chrome before 5.0.375.70 does not…
CVE-2023-22579 — Critical (CVSS 9.9): Due to improper parameter filtering in the sequalize js library, can a attacker peform injection.
CVE-2026-16919 — Critical (CVSS 9.8): IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to improper…
CVE-2026-71558 — Critical (CVSS 9.8): Heap type confusion vulnerability in Apache Fory C++ deserialization. This issue affects Apache Fory C++ versions from…
CVE-2026-64727 — Critical (CVSS 9.8): A type confusion issue was addressed with improved memory handling. This issue is fixed in macOS Tahoe 26.6, tvOS 26.6.…

Browse all CWE-843 vulnerabilities →