VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

arrayfire: vulnerability history, versions and safety

arrayfire is a package in the crates.io ecosystem. Vulert records 3 vulnerabilities for it across 10 releases, from Dec 2018 to Aug 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all arrayfire vulnerabilities

Vulert verdict on arrayfire 3.8.0 i

Updated on 23 Oct 2026

Good news: 3.8.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 57/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

What to do: Stay on 3.8.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.8.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.8.0 — unaffected i
  • Vulnerabilities on record 3 over 2 years · 0 in the last year i
  • Latest disclosure 25 Aug 2021 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 13 packages i
  • Stars 826 i
  • OpenSSF scorecard 2/10 i
  • Last release 69 months ago i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for arrayfire, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.8.0 10 Jan 2021 none BSD-3-Clause — Details →
3.7.2 06 Oct 2020 none BSD-3-Clause — Details →
3.7.1 09 Sep 2020 none BSD-3-Clause — Details →
3.7.0 14 Mar 2020 none BSD-3-Clause — Details →
3.6.3 28 Jan 2020 none BSD-3-Clause — Details →
3.6.2 25 Jul 2019 none BSD-3-Clause — Details →
3.6.1 18 Jun 2019 none BSD-3-Clause — Details →
3.6.0 27 Sep 2018 none BSD-3-Clause — Details →
3.5.0 28 Jun 2017 C1 BSD-3-Clause Yes Details →
3.4.3 10 Apr 2017 C1 BSD-3-Clause Yes Details →
3.4.2 26 Feb 2017 C1 BSD-3-Clause Yes Details →
3.4.1 11 Jan 2017 C1 BSD-3-Clause Yes Details →
3.4.0 15 Sep 2016 C1 BSD-3-Clause Yes Details →
3.3.2 29 Jul 2016 C1 BSD-3-Clause Yes Details →
3.3.1 08 Jun 2016 C1 BSD-3-Clause Yes Details →
3.3.0 20 May 2016 C1 BSD-3-Clause Yes Details →
3.2.0 10 Dec 2015 C1 BSD-3-Clause Yes Details →
3.2.0-rc0 14 Nov 2015 C1 BSD-3-Clause Yes Details →

All 18 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2021 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for arrayfire

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-20998: Memory Corruption in arrayfire 9.8 critical 3.6.0 18 Dec 2018
CVE-2018-20998: Memory Corruption Vulnerability in arrayfire 9.8 critical 3.6.0 18 Dec 2018
CVE-2018-20998: Memory Corruption in arrayfire 9.8 critical 3.6.0 25 Aug 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About arrayfire

Is arrayfire safe to use?

Vulert records 3 vulnerabilities for arrayfire in crates.io: 1 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is arrayfire's Vulert package health score?

Vulert scores arrayfire 57/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of arrayfire affected?

No. 3.8.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of arrayfire should I use?

3.8.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does arrayfire have?

3 vulnerabilities are recorded for arrayfire in the crates.io ecosystem: 1 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new arrayfire vulnerabilities disclosed?

0 vulnerabilities were recorded for arrayfire in the last 12 months, and the oldest entry in this database dates to 18 Dec 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of arrayfire are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.