NumPy 1.16 · Version Status
NumPy 1.16 End of Life Date
NumPy 1.16 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
NumPy 1.16 is past end of life. This version no longer receives security patches. 2037 days past EOL — migrate to a supported version immediately.
EOL Date
Jan 13, 2021
2037 days past EOL
Latest Release
1.16.6
Standard release
Release Date
Jan 14, 2019
NumPy 1.16 series
Lifecycle detail
NumPy 1.16 was released on January 14, 2019 and support ended on January 13, 2021 — a supported lifespan of 2 years, in line with the 2 years median for NumPy releases. The last patch it will ever receive is 1.16.6, published December 29, 2019 — 1 year and 1 month before support ended. It has been without security patches for 5 years and 7 months. 13 newer NumPy releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended NumPy 1.16 support is available
Commercial vendors offer security patches beyond EOL. Right now that coverage spans NumPy 1.26.x. Compare your options.
Compare Options →
| 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 1.16 end of life mean?
When NumPy 1.16 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 1.16 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to NumPy 2.5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does NumPy 1.16 reach end of life?
NumPy 1.16 reached end of life on January 13, 2021. This version is no longer receiving security patches.
Is NumPy 1.16 still supported?
No. NumPy 1.16 reached end of life on January 13, 2021 and is no longer receiving security patches.
What should I upgrade to from NumPy 1.16?
The recommended upgrade from NumPy 1.16 is
NumPy 2.5 — the latest actively supported version. Check the
NumPy full timeline for all supported versions.
What are the security risks of running NumPy 1.16 past EOL?
When NumPy 1.16 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.