CVE-2018-20998

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 37% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An issue was discovered in the arrayfire crate before 3.6.0 for Rust. Addition of the repr() attribute to an enum is mishandled, leading to memory corruption.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
73.6%
KEV
Not listed

Published

August 26, 2019

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Jun 8, 2026
No patch confirmed yet.
generic

RUSTSEC-2018-0011: arrayfire: Enum repr causing potential memory corruption › RustSec Advisory Database

https://rustsec.org/advisories/RUSTSEC-2018-0011.html

Affected Packages

(2 across 2 ecosystems)
crates.io(1)
PackageVulnerable rangeFixed inDependents
arrayfire3.6.0
PyPI(1)
PackageVulnerable rangeFixed inDependents
arrayfire3.0.20150914 ... 3.5.20170817 (20 versions)3.6.0

Frequently asked(5)

What is CVE-2018-20998?
CVE-2018-20998 is a critical vulnerability published on August 26, 2019. An issue was discovered in the arrayfire crate before 3.6.0 for Rust. Addition of the repr() attribute to an enum is mishandled, leading to memory corruption.
When was CVE-2018-20998 disclosed?
CVE-2018-20998 was first published in the National Vulnerability Database on August 26, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-20998 actively exploited?
CVE-2018-20998 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 73.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-20998?
CVE-2018-20998 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-20998?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-20998, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-20998

Explore →

Is Your Infrastructure Affected by CVE-2018-20998?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.