PatchTheCVECVE-2018-20998: An issue was discovered in the arrayfire crate before 3.6.0 for Rust
CVE-2018-20998 is a critical-severity flaw (CVSS 9.8) affecting arrayfire. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
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.7% (top 23%) |
| CISA exploited list | No |
| Weakness | CWE-119 |
| Published | 2019-08-26 |
| 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-2018-20998?
arrayfire: upgrade to 3.6.0. Exact commands for each OS are on this page.
Is CVE-2018-20998 being exploited?
CVE-2018-20998 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-2018-20998 affect?
CVE-2018-20998 affects arrayfire. Severity is critical (CVSS 9.8). 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.
How urgent is CVE-2018-20998?
Priority 58/100. Critical severity; Remotely exploitable, no login, no user action