Numpy 2.0 · Version Status
Numpy 2.0 End of Life Date
Numpy 2.0 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚡
Numpy 2.0 reaches end of life on June 17, 2026. Plan your migration now — 39 days remaining.
EOL Date
Jun 17, 2026
39 days remaining
Latest Release
2.0.2
Standard release
Release Date
Jun 16, 2024
Numpy 2.0 series
| Version | Latest | EOL Date | Status |
|---|
| 1.14 |
1.14.6 |
Jan 7, 2020 |
EOL |
| 1.15 |
1.15.4 |
Jul 23, 2020 |
EOL |
| 1.16 |
1.16.6 |
Jan 13, 2021 |
EOL |
| 1.17 |
1.17.5 |
Jul 26, 2021 |
EOL |
| 1.18 |
1.18.5 |
Dec 22, 2021 |
EOL |
| 1.19 |
1.19.5 |
Jun 21, 2022 |
EOL |
| 1.20 |
1.20.3 |
Jan 31, 2023 |
EOL |
| 1.21 |
1.21.6 |
Jun 23, 2023 |
EOL |
What does Numpy 2.0 end of life mean?
When Numpy 2.0 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Numpy 2.0 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Numpy 2.4 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Numpy 2.0 reach end of life?
Numpy 2.0 reached end of life on June 17, 2026. That is 39 days remaining.
Is Numpy 2.0 still supported?
Numpy 2.0 is still supported but approaching end of life on June 17, 2026. Begin planning your migration now.
What should I upgrade to from Numpy 2.0?
The recommended upgrade from Numpy 2.0 is
Numpy 2.4 — the latest actively supported version. Check the
Numpy full timeline for all supported versions.
What are the security risks of running Numpy 2.0 past EOL?
When Numpy 2.0 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Numpy should migrate immediately or implement compensating controls.