Vulnerability Database · PyPI · arrayfire · Version
arrayfire 3.5.20170817
3.5.20170817 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 3.8.0.
Critical 0 High 0 Medium 0 Low 0 Unrated 1
-
Released 17 Aug 2017
Licence non-standard
Also known from other sources 1
Newer releases 23
Database updated 23/Oct/2026
Release and licence data published by PyPI. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
arrayfire 3.5.20170817 vulnerabilities
1 vulnerability cover arrayfire 3.5.20170817. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2018-20998: Memory Corruption in arrayfire crate before 3.6.0 for Rust | N/A unrated | 3.6.0 | 26 Aug 2019 |
Looking for another version, or everything Vulert holds for arrayfire?
Questions
About arrayfire 3.5.20170817
Is arrayfire 3.5.20170817 vulnerable?
Yes. 1 vulnerability in the Vulert database cover arrayfire 3.5.20170817: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The upgrade Vulert recommends is 3.8.0, and each entry above names the fixed version to move to.
Which version of arrayfire should I use instead of 3.5.20170817?
3.8.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 3.5.20170817 the latest release of arrayfire?
No. 3.5.20170817 was published 17 Aug 2017, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor arrayfire for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the arrayfire version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.