Vulnerability Database · PyPI · Package report

joblib: vulnerability history, versions and safety

joblib is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 120 releases, from Sep 2022 to May 2024. 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
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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.

Vulert verdict on joblib 1.6.0 i

Updated on 23 Oct 2026

Careful: 1.6.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.6.0 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 17 May 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Depended on by 44,265 packages i
  • Stars 4,410 i
  • OpenSSF scorecard 6/10 i
  • Last release 1 month ago i
  • Licence BSD-3-Clause 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 joblib, 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
1.6.0 31 Aug 2026 U1 BSD-3-Clause No Details →
1.5.3 15 Dec 2025 U1 BSD-3-Clause No Details →
1.5.2 27 Aug 2025 U1 BSD-3-Clause No Details →
1.5.1 23 May 2025 U1 BSD-3-Clause No Details →
1.5.0 03 May 2025 U1 BSD-3-Clause No Details →
1.4.2 02 May 2024 U1 BSD-3-Clause No Details →
1.4.0 08 Apr 2024 U1 BSD-3-Clause No Details →
1.3.2 09 Aug 2023 U1 BSD-3-Clause No Details →
1.3.1 29 Jun 2023 U1 BSD-3-Clause No Details →
1.3.0 28 Jun 2023 U1 BSD-3-Clause No Details →
1.1.1 10 Oct 2022 C1 U2 non-standard No Details →
1.2.0 16 Sep 2022 U1 non-standard No Details →
1.1.0 07 Oct 2021 C1 U2 non-standard No Details →
1.1.0a0 07 Oct 2021 C1 U2 non-standard No Details →
1.0.1 09 Feb 2021 C1 U2 non-standard No Details →
1.0.0 14 Dec 2020 C1 U2 non-standard No Details →
0.17.0 02 Oct 2020 C1 U2 non-standard No Details →
0.16.0 01 Jul 2020 C1 U2 non-standard No Details →
0.15.1 16 May 2020 C1 U2 non-standard No Details →
0.15.0 15 May 2020 C1 U2 non-standard No Details →
0.14.1 10 Dec 2019 C1 U2 non-standard No Details →
0.14.0 01 Oct 2019 C1 U2 non-standard No Details →
0.13.2 13 Feb 2019 C1 U2 non-standard No Details →
0.13.1 11 Jan 2019 C1 U2 non-standard No Details →
0.13.0 06 Nov 2018 C1 U2 non-standard No Details →
0.12.5 13 Sep 2018 C1 U2 non-standard No Details →
0.12.4 05 Sep 2018 C1 U2 non-standard No Details →
0.12.3 30 Aug 2018 C1 U2 non-standard No Details →
0.12.2 02 Aug 2018 C1 U2 non-standard No Details →
0.12.1 17 Jul 2018 C1 U2 non-standard No Details →
0.12.0 22 Jun 2018 C1 U2 non-standard No Details →
0.11.0 02 Mar 2017 C1 U1 non-standard No Details →
0.11.0a3 02 Mar 2017 C1 U1 — No Details →
0.10.3 18 Oct 2016 C1 U2 — No Details →
0.10.2 29 Aug 2016 C1 U2 — No Details →
0.10.0 13 Jul 2016 C1 U2 — No Details →
0.9.4 18 Jan 2016 C1 U2 — No Details →
0.9.3 30 Oct 2015 C1 U2 — No Details →
0.9.2 14 Oct 2015 C1 U2 — No Details →
0.9.1 14 Oct 2015 C1 U2 — No Details →
0.9.0b4 27 Aug 2015 C1 U2 — No Details →
0.9.0b3 22 Jul 2015 C1 U2 — No Details →
0.9.0b2 29 Jun 2015 C1 U2 — No Details →
0.8.4 24 Nov 2014 C1 U2 — No Details →
0.8.3.post1 24 Aug 2014 C1 U1 — No Details →
0.8.3 20 Aug 2014 C1 U2 — No Details →
0.8.2 01 Jul 2014 C1 U2 — No Details →
0.8.1 04 Jun 2014 C1 U2 — No Details →
0.8.0 28 May 2014 C1 U2 — No Details →
0.8.0a3 15 Jan 2014 C1 U2 — No Details →
0.8.0a2 23 Dec 2013 C1 U2 — No Details →
0.8.0a0 20 Dec 2013 C1 U1 — No Details →
0.7.1 26 Jul 2013 C1 U2 — No Details →
0.7.0d 08 Feb 2013 C1 U2 — No Details →
0.7.0rc0 07 Feb 2013 C1 U1 — No Details →
0.7.0b0 20 Nov 2012 C1 U1 — No Details →
0.7.0a0 19 Nov 2012 C1 U1 — No Details →
0.6.5 21 Sep 2012 C1 U2 — No Details →
0.6.4 07 May 2012 C1 U2 — No Details →
0.6.3 15 Feb 2012 C1 U2 — No Details →
0.6.2 07 Feb 2012 C1 U2 — No Details →
0.6.1 05 Feb 2012 C1 U2 — No Details →
0.6.0 05 Feb 2012 C1 U2 — No Details →
0.6.0b3 12 Jan 2012 C1 U2 — No Details →
0.6.0b2 07 Jan 2012 C1 U2 — No Details →
0.6.0b0 07 Jan 2012 C1 U1 — No Details →
0.6.0a0 03 Jan 2012 C1 U1 — No Details →
0.5.7 28 Dec 2011 C1 U2 — No Details →
0.5.7.dev0 28 Dec 2011 C1 U1 — No Details →
0.5.7b0.dev0 25 Dec 2011 C1 U1 — No Details →
0.5.7a0.dev0 25 Dec 2011 C1 U1 — No Details →
0.5.6.dev0 18 Dec 2011 C1 U1 — No Details →
0.5.5.dev0 20 Oct 2011 C1 U1 — No Details →
0.5.4.dev0 29 Sep 2011 C1 U1 — No Details →
0.5.3.dev0 25 Jun 2011 C1 U1 — No Details →
0.5.2.dev0 25 Jun 2011 C1 U1 — No Details →
0.5.1.dev0 13 Apr 2011 C1 U1 — No Details →
0.5.0.dev0 01 Apr 2011 C1 U1 — No Details →
0.5.0a0.dev0 22 Mar 2011 C1 U1 — No Details →
0.4.6.dev0 21 Nov 2010 C1 U1 — No Details →
0.4.5.dev0 16 Sep 2010 C1 U1 — No Details →
0.4.4.dev0 23 Aug 2010 C1 U1 — No Details →
0.4.3.dev0 22 Jul 2010 C1 U1 — No Details →
0.4.2.dev0 16 Jul 2010 C1 U1 — No Details →
0.4.1.dev0 03 Jul 2010 C1 U1 — No Details →
0.4.0.dev0 22 Jun 2010 C1 U1 — No Details →
0.3.7.dev0 22 Jun 2010 C1 U1 — No Details →
0.3.6.dev0 07 May 2010 C1 U1 — No Details →
0.3.5.dev0 25 Apr 2010 C1 U1 — No Details →
0.3.4.dev0 08 Dec 2009 C1 U1 — No Details →
0.3.3rc0.dev0 16 Sep 2009 C1 U1 — No Details →
0.3.3b0.dev0 14 Sep 2009 C1 U1 — No Details →
0.3.3a0.dev0 11 Sep 2009 C1 U1 — No Details →
0.3.2.dev0 10 Sep 2009 C1 U1 — No Details →
0.3.2g.dev 03 Sep 2009 C1 U2 — No Details →
0.3.2f.dev 02 Sep 2009 C1 U2 — No Details →
0.3.2e.dev 02 Sep 2009 C1 U2 — No Details →
0.3.2d.dev 01 Sep 2009 C1 U2 — No Details →
0.3.2rc0.dev0 01 Sep 2009 C1 U1 — No Details →
0.3.2b0.dev0 01 Sep 2009 C1 U1 — No Details →
0.3.2a0.dev0 01 Sep 2009 C1 U1 — No Details →
0.3.1a0.dev0 01 Sep 2009 C1 U1 — No Details →
0.3.0a0.dev0 01 Sep 2009 C1 U1 — No Details →
0.2.0a0.dev0 22 Mar 2009 C1 U1 — No Details →
0.1.0a0.dev0 26 Oct 2008 C1 U1 — No Details →
0.10.0-py3.5 — C1 U1 — No Details →
0.10.2-py2.7 — C1 U1 — No Details →
0.10.3-py3.5 — C1 U1 — No Details →
0.1a.dev-py2.5 — C1 U1 — No Details →
0.2a.dev-py2.5 — C1 U1 — No Details →
0.3.5.dev-py2.6 — C1 U1 — No Details →
0.3.6.dev-py2.5 — C1 U1 — No Details →
0.4.0.dev-py2.6 — C1 U1 — No Details →
0.4.1.dev-py2.6 — C1 U1 — No Details →
0.4.2.dev-py2.5 — C1 U1 — No Details →
0.4.3.dev-py2.5 — C1 U1 — No Details →
0.4.3.dev-py2.6 — C1 U1 — No Details →
0.4.4.dev-py2.6 — C1 U1 — No Details →
0.4.5.dev-py2.6 — C1 U1 — No Details →
0.4.6.dev-py2.6 — C1 U1 — No Details →

The newest 120 of 166 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2024 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 joblib

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →

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 joblib

Is joblib safe to use?

Vulert records 3 vulnerabilities for joblib in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is joblib's Vulert package health score?

Vulert scores joblib 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of joblib affected?

Yes. 1.6.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of joblib should I use?

1.6.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 joblib have?

3 vulnerabilities are recorded for joblib in the PyPI 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 joblib vulnerabilities disclosed?

0 vulnerabilities were recorded for joblib in the last 12 months, and the oldest entry in this database dates to 26 Sep 2022. 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 joblib 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 joblib for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the joblib version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.