NumPy End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all NumPy versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.14 | 1.14.6 | Jan 6, 2018 | Jan 7, 2020 | 2359 days past EOL | EOL |
| 1.15 | 1.15.4 | Jul 23, 2018 | Jul 23, 2020 | 2161 days past EOL | EOL |
| 1.16 | 1.16.6 | Jan 14, 2019 | Jan 13, 2021 | 1987 days past EOL | EOL |
| 1.17 | 1.17.5 | Jul 26, 2019 | Jul 26, 2021 | 1793 days past EOL | EOL |
| 1.18 | 1.18.5 | Dec 22, 2019 | Dec 22, 2021 | 1644 days past EOL | EOL |
| 1.19 | 1.19.5 | Jun 20, 2020 | Jun 21, 2022 | 1463 days past EOL | EOL |
| 1.20 | 1.20.3 | Jan 30, 2021 | Jan 31, 2023 | 1239 days past EOL | EOL |
| 1.21 | 1.21.6 | Jun 22, 2021 | Jun 23, 2023 | 1096 days past EOL | EOL |
| 1.22 | 1.22.4 | Dec 31, 2021 | Jan 1, 2024 | 904 days past EOL | EOL |
| 1.23 | 1.23.5 | Jun 22, 2022 | Jun 24, 2024 | 729 days past EOL | EOL |
| 1.24 | 1.24.4 | Dec 18, 2022 | Dec 19, 2024 | 551 days past EOL | EOL |
| 1.25 | 1.25.2 | Jun 17, 2023 | Jun 18, 2025 | 370 days past EOL | EOL |
| 1.26 | 1.26.4 | Sep 16, 2023 | Sep 17, 2025 | 279 days past EOL | EOL |
| 2.0 | 2.0.2 | Jun 16, 2024 | Jun 17, 2026 | 6 days past EOL | EOL |
| 2.1 | 2.1.3 | Aug 18, 2024 | Aug 19, 2026 | 57 days remaining | Warning |
| 2.2 | 2.2.6 | Dec 8, 2024 | Dec 9, 2026 | 169 days remaining | Warning |
| 2.3 | 2.3.5 | Jun 7, 2025 | Jun 8, 2027 | 350 days remaining | Active |
| 2.4 | 2.4.6 | Dec 20, 2025 | Dec 21, 2027 | 546 days remaining | Active |
What does NumPy end of life mean for your organization?
When a version of NumPy reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL NumPy should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL NumPy versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →