VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

numexpr: vulnerability history, versions and safety

numexpr is a package in the PyPI ecosystem. Vulert records 1 vulnerability for it across 62 releases, first recorded in Sep 2023. 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 numexpr vulnerabilities

Vulert verdict on numexpr 2.14.2 i

Updated on 22 Oct 2026

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

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

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

  • Current release 2.14.2 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 01 Sep 2023 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 3,296 packages i
  • Stars 2,544 i
  • OpenSSF scorecard 4/10 i
  • Last release 3 months ago i
  • Licence MIT 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 numexpr, 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.14.2 18 Jul 2026 none MIT — Details →
2.14.1 13 Oct 2025 none MIT — Details →
2.14.0 13 Oct 2025 none MIT — Details →
2.13.1 30 Sep 2025 none MIT — Details →
2.13.0 24 Sep 2025 none MIT — Details →
2.12.1 11 Sep 2025 none MIT — Details →
2.12.0 10 Sep 2025 none MIT — Details →
2.11.0 09 Jun 2025 none MIT — Details →
2.10.2 23 Nov 2024 none MIT — Details →
2.10.1 20 Jun 2024 none MIT — Details →
2.10.0 02 Apr 2024 none MIT — Details →
2.9.0 26 Jan 2024 none MIT — Details →
2.8.8 11 Dec 2023 none MIT — Details →
2.8.7 26 Sep 2023 none MIT — Details →
2.8.6 12 Sep 2023 none MIT — Details →
2.8.5 06 Aug 2023 none MIT — Details →
2.8.4 26 Oct 2022 U1 MIT Yes Details →
2.8.3 25 Jun 2022 U1 MIT Yes Details →
2.8.1 10 Dec 2021 U1 — Yes Details →
2.8.0 02 Dec 2021 U1 MIT Yes Details →
2.7.3 03 Mar 2021 U1 MIT Yes Details →
2.7.2 29 Dec 2020 U1 MIT Yes Details →
2.7.1 05 Jan 2020 U1 MIT Yes Details →
2.7.0 24 Dec 2019 U1 MIT Yes Details →
2.6.9 21 Dec 2018 U1 MIT Yes Details →
2.6.8 19 Aug 2018 U1 MIT Yes Details →
2.6.7 13 Aug 2018 U1 MIT Yes Details →
2.6.6 16 Jul 2018 U1 MIT Yes Details →
2.6.6.dev0 01 May 2018 U1 MIT Yes Details →
2.6.5 01 May 2018 U1 MIT Yes Details →
2.6.4 15 Sep 2017 U1 MIT Yes Details →
2.6.3 14 Sep 2017 U1 MIT Yes Details →
2.6.2 29 Jan 2017 U1 MIT Yes Details →
2.6.1 17 Jul 2016 U1 MIT Yes Details →
2.6.0 01 Jun 2016 U1 MIT Yes Details →
2.5.2 07 Apr 2016 U1 MIT Yes Details →
2.5.1 31 Mar 2016 U1 MIT Yes Details →
2.5.0 06 Feb 2016 U1 MIT Yes Details →
2.4.6 02 Nov 2015 U1 MIT Yes Details →
2.4.5 02 Nov 2015 U1 MIT Yes Details →
2.4.4 14 Sep 2015 U1 MIT Yes Details →
2.4.3 27 Apr 2015 U1 MIT Yes Details →
2.4.2 22 Apr 2015 U1 MIT Yes Details →
2.4.1 14 Apr 2015 U1 MIT Yes Details →
2.4.0 13 Apr 2014 U1 MIT Yes Details →
2.4.0rc2 07 Apr 2014 U1 MIT Yes Details →
2.4.0rc1 06 Apr 2014 U1 MIT Yes Details →
2.3.1 18 Feb 2014 U1 MIT Yes Details →
2.3.0 26 Jan 2014 U1 MIT Yes Details →
2.3.0rc1 24 Jan 2014 U1 MIT Yes Details →
2.2.2 27 Sep 2013 U1 MIT Yes Details →
2.2.1 08 Sep 2013 U1 MIT Yes Details →
2.0.1 03 May 2013 U1 MIT Yes Details →
2.1.0 27 Apr 2013 U1 MIT Yes Details →
1.4.2 25 Jan 2011 U1 MIT Yes Details →
1.4.1 20 Oct 2010 U1 MIT Yes Details →
1.4.0 02 Aug 2010 U1 MIT Yes Details →
1.3.1 23 Jun 2009 U1 MIT Yes Details →
1.3.0 02 Jun 2009 U1 MIT Yes Details →
1.1.1 23 Jan 2009 U1 — Yes Details →
1.1.1.win32-py2.4 — U1 — Yes Details →
1.1.1.win32-py2.5 — U1 — Yes Details →
1.3.1.win32-py2.4 — U1 — Yes Details →
1.3.1.win32-py2.5 — U1 — Yes Details →
1.3.1.win32-py2.6 — U1 — Yes Details →
1.3.win32-py2.4 — U1 — Yes Details →
1.3.win32-py2.5 — U1 — Yes Details →
1.3.win32-py2.6 — U1 — Yes Details →
1.4.1.win-amd64-py2.6 — U1 — Yes Details →
1.4.1.win-amd64-py2.7 — U1 — Yes Details →
1.4.1.win32-py2.6 — U1 — Yes Details →
1.4.1.win32-py2.7 — U1 — Yes Details →
1.4.2.win-amd64-py2.6 — U1 — Yes Details →
1.4.2.win-amd64-py2.7 — U1 — Yes Details →
1.4.2.win32-py2.6 — U1 — Yes Details →
1.4.2.win32-py2.7 — U1 — Yes Details →
1.4.win-amd64-py2.6 — U1 — Yes Details →
1.4.win32-py2.6 — U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 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 numexpr

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-39631: Arbitrary Code Execution in numexpr 9.8 critical 2.8.5 01 Sep 2023

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 numexpr

Is numexpr safe to use?

Vulert records 1 vulnerabilities for numexpr 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 numexpr's Vulert package health score?

Vulert scores numexpr 80/100, which reads as in good shape. 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 numexpr affected?

No. 2.14.2, 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 numexpr should I use?

2.14.2 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 numexpr have?

1 vulnerability is recorded for numexpr 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 numexpr vulnerabilities disclosed?

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

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