NumPy 2.3 · Version Status
NumPy 2.3 End of Life Date
NumPy 2.3 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
NumPy 2.3 is actively supported. EOL date: June 8, 2027.
📅 Get reminded before NumPy 2.3 reaches EOL on June 8, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Jun 8, 2027
237 days remaining
Latest Release
2.3.5
Standard release
Release Date
Jun 7, 2025
NumPy 2.3 series
Lifecycle detail
NumPy 2.3 was released on June 7, 2025 and support is scheduled to end on June 8, 2027 — a planned supported lifespan of 2 years, in line with the 2 years median for NumPy releases. Its most recent patch is 2.3.5, published November 16, 2025.
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 →
| 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.3 end of life mean?
When NumPy 2.3 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running NumPy 2.3 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
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 2.3 reach end of life?
NumPy 2.3 reaches end of life on June 8, 2027. That is 237 days remaining.
Is NumPy 2.3 still supported?
Yes, NumPy 2.3 is currently supported. The EOL date is June 8, 2027.
What should I upgrade to from NumPy 2.3?
The recommended upgrade from NumPy 2.3 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 2.3 past EOL?
When NumPy 2.3 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL NumPy should migrate immediately or implement compensating controls.