Enum repr causing potential memory corruption

Answer in brief

CVE-2018-20998 records a Critical severity (CVSS 9.8) vulnerability in Enum repr causing potential memory corruption. The current sources do not mark it as known exploited. The current feed maps arrayfire (crates.io). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Dec 18, 2018Updated Sep 25, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 25, 2026

Upstream Advisory

Key facts

Risk: Critical · CVSS 9.8
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps arrayfire (crates.io). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
arrayfirecrates.io	>=0.0.0-0 <3.6.0	3.6.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for arrayfire.
Review the reported fix. Update arrayfire to 3.6.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Dec 18, 2018
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 25, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.