VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

arrayfire: vulnerability history, versions and safety

arrayfire is a package in the PyPI ecosystem. Vulert records 1 vulnerability for it across 20 releases, first recorded in Aug 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
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 1.

Package health score 69/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Not enough data

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 1 over 1 year · 0 in the last year i
  • Latest disclosure 26 Aug 2019 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 8 packages i
  • Last release 56 months ago i

Version list, release dates, licence and dependants published by PyPI, 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 22 Feb 2022 none — — Details →
3.8.0rc1 05 Mar 2021 none — — Details →
3.6.20181017 18 Oct 2018 none non-standard — Details →
3.6.0 17 Oct 2018 none non-standard — Details →
3.5.20170817 17 Aug 2017 U1 non-standard Yes Details →
3.5.20170721 21 Jul 2017 U1 non-standard Yes Details →
3.5.20170718 18 Jul 2017 U1 non-standard Yes Details →
3.4.20170222 22 Feb 2017 U1 non-standard Yes Details →
3.4.20161126 27 Nov 2016 U1 non-standard Yes Details →
3.4.20160925 25 Sep 2016 U1 non-standard Yes Details →
3.3.20160624.post1 25 Jun 2016 U1 non-standard Yes Details →
3.3.20160624 25 Jun 2016 U1 non-standard Yes Details →
3.3.20160516 16 May 2016 U1 non-standard Yes Details →
3.3.20160510 10 May 2016 U1 non-standard Yes Details →
3.3.20160427.post1 27 Apr 2016 U1 non-standard Yes Details →
3.3.20160427 27 Apr 2016 U1 non-standard Yes Details →
3.3.20160328 28 Mar 2016 U1 non-standard Yes Details →
3.3.20160320 20 Mar 2016 U1 non-standard Yes Details →
3.2.20151224.post1 25 Dec 2015 U1 non-standard Yes Details →
3.2.20151214 14 Dec 2015 U1 non-standard Yes Details →
3.2.20151211 11 Dec 2015 U1 non-standard Yes Details →
3.1.20151111 11 Nov 2015 U1 non-standard Yes Details →
3.0.20150914 14 Sep 2015 U1 non-standard Yes Details →
3.4.20160925-py3.5 — U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1

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

03 Vulnerabilities

Recorded vulnerabilities for arrayfire

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 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

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 1 vulnerabilities for arrayfire in PyPI: 0 critical, 0 high, 0 medium and 0 low, plus 1 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 69/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?

1 vulnerability is recorded for arrayfire in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 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 26 Aug 2019. 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.