Vulnerability Database · PyPI · numpy · Version

numpy 1.9.3

1.9.3 is affected by 14 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 2.5.4.

Critical 2 High 2 Medium 3 Low 0 Unrated 7

Released 21 Sep 2015 Licence 0BSD AND BSD-3-Clause AND CC0-1.0 AND MIT AND Zlib Also known from other sources 0 Newer releases 135 Database updated 23/Oct/2026

Release and licence data published by PyPI. 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 Vulnerabilities affecting this version

numpy 1.9.3 vulnerabilities

14 vulnerabilities cover numpy 1.9.3. Scroll the table for all of them, or open the full list in the database.

Looking for another version, or everything Vulert holds for numpy?

All versions → Full vulnerability list →

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 1.9.3

Is numpy 1.9.3 vulnerable?

Yes. 14 vulnerabilities in the Vulert database cover numpy 1.9.3: 2 critical, 2 high, 3 medium and 0 low, plus 7 not yet rated. The upgrade Vulert recommends is 2.5.4, and each entry above names the fixed version to move to.

Which version of numpy should I use instead of 1.9.3?

2.5.4 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 1.9.3 the latest release of numpy?

No. 1.9.3 was published 21 Sep 2015, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

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.