Rust advisories / arrayfire
Vulnerability CriticalRUSTSEC-2018-0011 · arrayfire
RUSTSEC-2018-0011: Enum repr causing potential memory corruption
Short answerA security vulnerability in the arrayfire crate: Enum repr causing potential memory corruption. Critical severity (CVSS 9.8). Fixed in 3.6.0: update to a fixed version.
| Crate | arrayfire |
|---|---|
| Type | Vulnerability (memory-corruption) |
| Affected versions | Before 3.6.0. |
| Fixed in | 3.6.0 |
| Severity | Critical, CVSS 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Published | 2018-12-18 |
| Last changed | 2026-09-25 |
| Also known as | CVE-2018-20998, GHSA-69fv-gw6g-8ccg |
What to do
- See which version you have:
cargo tree -i arrayfire(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p arrayfire. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplearrayfire = "3.6.0") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
The attribute repr() added to enums to be compatible with C-FFI caused memory corruption on MSVC toolchain.
arrayfire crates <= version 3.5.0 do not have this issue when used with Rust versions 1.27 or earlier. The issue only started to appear since Rust version 1.28.
The issue seems to be interlinked with which version of Rust is being used.
The issue was fixed in crate 3.6.0.
References
- Package: crates.io/crates/arrayfire
- Advisory: rustsec.org/advisories/RUSTSEC-2018-0011.html
- Web: github.com/arrayfire/arrayfire-rust/pull/177
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?