VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

numpy: vulnerability history, versions and safety

numpy is a package in the PyPI ecosystem. Vulert records 18 vulnerabilities for it across 120 releases, from Aug 2017 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
18 vulnerabilities recorded C2 H4 M3 U9
i
2 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.

See all numpy vulnerabilities

Vulert verdict on numpy 2.5.4 i

Updated on 22 Oct 2026

Careful: 2.5.4 has 2 known vulnerabilities, and 2 have 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 Active

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 2.5.4 — affected i
  • Vulnerabilities on record 18 over 4 years · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i
  • Depended on by 173,346 packages i
  • Stars 33,077 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib 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 numpy, 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
2.5.4 10 Oct 2026 C2 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib No Details →
2.5.3 06 Sep 2026 C2 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib No Details →
2.5.2 09 Aug 2026 C2 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib No Details →
2.5.1 04 Jul 2026 C2 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib No Details →
2.5.0 21 Jun 2026 C2 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib No Details →
2.5.0rc1 02 Jun 2026 C2 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib No Details →
2.4.6 18 May 2026 C2 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib No Details →
2.4.5 15 May 2026 C2 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib No Details →
2.4.4 29 Mar 2026 C2 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib No Details →
2.4.3 09 Mar 2026 C2 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib No Details →
2.4.2 31 Jan 2026 C2 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib No Details →
2.4.1 10 Jan 2026 C2 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib No Details →
2.4.0 20 Dec 2025 C2 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib No Details →
2.4.0rc1 03 Dec 2025 C2 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib No Details →
2.3.5 16 Nov 2025 C2 non-standard No Details →
2.3.4 15 Oct 2025 C2 non-standard No Details →
2.3.3 09 Sep 2025 C2 non-standard No Details →
2.3.2 24 Jul 2025 C2 non-standard No Details →
2.3.1 21 Jun 2025 C2 non-standard No Details →
2.3.0 07 Jun 2025 C2 non-standard No Details →
2.2.6 17 May 2025 C2 non-standard No Details →
2.2.5 19 Apr 2025 C2 non-standard No Details →
2.2.4 16 Mar 2025 C2 non-standard No Details →
2.2.3 13 Feb 2025 C2 non-standard No Details →
2.2.2 18 Jan 2025 C2 non-standard No Details →
2.2.1 21 Dec 2024 C2 non-standard No Details →
2.2.0 08 Dec 2024 C2 non-standard No Details →
2.1.3 02 Nov 2024 C2 non-standard No Details →
2.1.2 05 Oct 2024 C2 non-standard No Details →
2.1.1 03 Sep 2024 C2 non-standard No Details →
2.0.2 26 Aug 2024 C2 non-standard No Details →
2.1.0 18 Aug 2024 C2 non-standard No Details →
2.0.1 21 Jul 2024 C2 non-standard No Details →
2.0.0 16 Jun 2024 C2 non-standard No Details →
1.26.4 05 Feb 2024 C2 non-standard No Details →
1.26.3 02 Jan 2024 C2 non-standard No Details →
1.26.2 12 Nov 2023 C2 non-standard No Details →
1.26.1 14 Oct 2023 C2 non-standard No Details →
1.26.0 16 Sep 2023 C2 non-standard No Details →
1.25.2 31 Jul 2023 C2 BSD-3-Clause No Details →
1.25.1 08 Jul 2023 C2 BSD-3-Clause No Details →
1.24.4 26 Jun 2023 C2 BSD-3-Clause No Details →
1.25.0 17 Jun 2023 C2 BSD-3-Clause No Details →
1.24.3 22 Apr 2023 C2 BSD-3-Clause No Details →
1.24.2 05 Feb 2023 C2 BSD-3-Clause No Details →
1.24.1 26 Dec 2022 C2 BSD-3-Clause No Details →
1.24.0 18 Dec 2022 C2 BSD-3-Clause No Details →
1.23.5 20 Nov 2022 C2 non-standard No Details →
1.23.4 12 Oct 2022 C2 non-standard No Details →
1.23.3 09 Sep 2022 C2 non-standard No Details →
1.23.2 14 Aug 2022 C2 non-standard No Details →
1.23.1 09 Jul 2022 C2 non-standard No Details →
1.23.0 22 Jun 2022 C2 non-standard No Details →
1.22.4 20 May 2022 C2 non-standard No Details →
1.21.6 12 Apr 2022 M1 non-standard Yes Details →
1.22.3 07 Mar 2022 C2 non-standard No Details →
1.22.2 04 Feb 2022 C2 non-standard No Details →
1.22.1 14 Jan 2022 C2 non-standard No Details →
1.22.0 31 Dec 2021 C2 non-standard No Details →
1.21.5 20 Dec 2021 M1 non-standard Yes Details →
1.21.4 05 Nov 2021 M1 non-standard Yes Details →
1.21.3 20 Oct 2021 M1 non-standard Yes Details →
1.21.2 15 Aug 2021 M1 non-standard Yes Details →
1.21.1 18 Jul 2021 M1 non-standard Yes Details →
1.21.0 22 Jun 2021 M1 non-standard Yes Details →
1.20.3 10 May 2021 M2 non-standard Yes Details →
1.20.2 27 Mar 2021 M2 non-standard Yes Details →
1.20.1 07 Feb 2021 M2 non-standard Yes Details →
1.20.0 30 Jan 2021 M2 non-standard Yes Details →
1.19.5 05 Jan 2021 M2 non-standard Yes Details →
1.19.4 02 Nov 2020 M2 non-standard Yes Details →
1.19.3 29 Oct 2020 M2 non-standard Yes Details →
1.19.2 10 Sep 2020 M2 non-standard Yes Details →
1.19.1 21 Jul 2020 M2 non-standard Yes Details →
1.19.0 20 Jun 2020 M2 U1 non-standard Yes Details →
1.18.5 04 Jun 2020 H1 M3 U2 non-standard Yes Details →
1.18.4 03 May 2020 H1 M3 U2 non-standard Yes Details →
1.18.3 19 Apr 2020 H1 M3 U2 non-standard Yes Details →
1.18.2 17 Mar 2020 H1 M3 U2 non-standard Yes Details →
1.18.1 06 Jan 2020 H1 M3 U2 non-standard Yes Details →
1.17.5 01 Jan 2020 H1 M3 U2 non-standard Yes Details →
1.16.6 29 Dec 2019 H1 M3 U2 non-standard Yes Details →
1.18.0 22 Dec 2019 H1 M3 U2 non-standard Yes Details →
1.17.4 11 Nov 2019 H1 M3 U2 non-standard Yes Details →
1.17.3 17 Oct 2019 H1 M3 U2 non-standard Yes Details →
1.17.2 07 Sep 2019 H1 M3 U2 non-standard Yes Details →
1.16.5 28 Aug 2019 H1 M3 U2 non-standard Yes Details →
1.17.1 27 Aug 2019 H1 M3 U2 non-standard Yes Details →
1.17.0 26 Jul 2019 H1 M3 U2 non-standard Yes Details →
1.16.4 28 May 2019 H1 M3 U2 non-standard Yes Details →
1.16.3 22 Apr 2019 H1 M3 U2 non-standard Yes Details →
1.16.2 26 Feb 2019 H1 M3 U2 non-standard Yes Details →
1.16.1 31 Jan 2019 H1 M3 U2 non-standard Yes Details →
1.16.0 14 Jan 2019 C2 H1 M3 U4 non-standard No Details →
1.15.4 04 Nov 2018 C2 H1 M3 U4 non-standard No Details →
1.15.3 22 Oct 2018 C2 H1 M3 U4 non-standard No Details →
1.14.6 23 Sep 2018 C2 H1 M3 U4 non-standard No Details →
1.15.2 23 Sep 2018 C2 H1 M3 U4 non-standard No Details →
1.15.1 21 Aug 2018 C2 H1 M3 U4 non-standard No Details →
1.15.0 23 Jul 2018 C2 H1 M3 U4 non-standard No Details →
1.14.5 29 Jun 2018 C2 H1 M3 U4 — No Details →
1.14.4 06 Jun 2018 C2 H1 M3 U4 — No Details →
1.14.3 28 Apr 2018 C2 H1 M3 U4 — No Details →
1.14.2 12 Mar 2018 C2 H1 M3 U4 — No Details →
1.14.1 21 Feb 2018 C2 H1 M3 U4 — No Details →
1.14.0 07 Jan 2018 C2 H1 M3 U4 — No Details →
1.13.3 29 Sep 2017 C2 H1 M3 U4 — No Details →
1.13.1 07 Jul 2017 C2 H2 M3 U5 — No Details →
1.13.0 07 Jun 2017 C2 H2 M3 U5 — No Details →
1.12.1 18 Mar 2017 C2 H2 M3 U5 — No Details →
1.12.0 15 Jan 2017 C2 H2 M3 U5 — No Details →
1.11.3 19 Dec 2016 C2 H2 M3 U5 — No Details →
1.11.2 04 Oct 2016 C2 H2 M3 U5 — No Details →
1.11.1 26 Jun 2016 C2 H2 M3 U5 — No Details →
1.11.0 27 Mar 2016 C2 H2 M3 U5 — No Details →
1.10.4 07 Jan 2016 C2 H2 M3 U5 — No Details →
1.10.2 14 Dec 2015 C2 H2 M3 U5 — No Details →
1.10.1 12 Oct 2015 C2 H2 M3 U5 — No Details →
1.9.3 21 Sep 2015 C2 H2 M3 U7 — No Details →
1.9.2 01 Mar 2015 C2 H2 M3 U7 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 2
  • 2019 2
  • 2021 5
  • 2022 8

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

03 Vulnerabilities

Recorded vulnerabilities for numpy

The 5 most severe of 18 vulnerabilities recorded for this package

Search all 18 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-6446: Numpy Deserialization of Untrusted Data 9.8 critical No fix published 24 May 2022
CVE-2019-6446: Unsafe Usage of Pickle Module in NumPy 9.8 critical No fix published 24 May 2022
CVE-2017-12852: Numpy missing input validation 7.5 high 1.13.3 13 May 2022
CVE-2021-41495: NumPy NULL Pointer Dereference 7.5 high 1.19 08 Feb 2022
CVE-2014-1859: Numpy arbitrary file write via symlink attack 5.5 high 1.8.1 14 May 2022

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 numpy

Is numpy safe to use?

Vulert records 18 vulnerabilities for numpy in PyPI: 2 critical, 4 high, 3 medium and 0 low, plus 9 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is numpy's Vulert package health score?

Vulert scores numpy 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 numpy affected?

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

Which version of numpy should I use?

2.5.4 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 numpy have?

18 vulnerabilities are recorded for numpy in the PyPI ecosystem: 2 critical, 4 high, 3 medium and 0 low, plus 9 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 numpy vulnerabilities disclosed?

0 vulnerabilities were recorded for numpy in the last 12 months, and the oldest entry in this database dates to 15 Aug 2017. 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 numpy 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 numpy for upcoming vulnerabilities?

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