Complete end-of-life dates, support windows, and security status for all Python versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.6 | 2.6.9 | Oct 1, 2008 | Oct 29, 2013 | 4575 days past EOL | EOL |
| 3.0 | 3.0.1 | Dec 3, 2008 | Jun 27, 2009 | 6160 days past EOL | EOL |
| 3.1 | 3.1.5 | Jun 27, 2009 | Apr 9, 2012 | 5143 days past EOL | EOL |
| 2.7 | 2.7.18 | Jul 3, 2010 | Jan 1, 2020 | 2320 days past EOL | EOL |
| 3.2 | 3.2.6 | Feb 20, 2011 | Feb 20, 2016 | 3731 days past EOL | EOL |
| 3.3 | 3.3.7 | Sep 29, 2012 | Sep 29, 2017 | 3144 days past EOL | EOL |
| 3.4 | 3.4.10 | Mar 16, 2014 | Mar 18, 2019 | 2609 days past EOL | EOL |
| 3.5 | 3.5.10 | Sep 13, 2015 | Sep 30, 2020 | 2047 days past EOL | EOL |
| 3.6 | 3.6.15 | Dec 23, 2016 | Dec 23, 2021 | 1598 days past EOL | EOL |
| 3.7 | 3.7.17 | Jun 27, 2018 | Jun 27, 2023 | 1047 days past EOL | EOL |
| 3.8 | 3.8.20 | Oct 14, 2019 | Oct 7, 2024 | 579 days past EOL | EOL |
| 3.9 | 3.9.25 | Oct 5, 2020 | Oct 31, 2025 | 190 days past EOL | EOL |
| 3.10 | 3.10.20 | Oct 4, 2021 | Oct 31, 2026 | 175 days remaining | Warning |
| 3.11 | 3.11.15 | Oct 24, 2022 | Oct 31, 2027 | 540 days remaining | Active |
| 3.12 | 3.12.13 | Oct 2, 2023 | Oct 31, 2028 | 906 days remaining | Active |
| 3.13 | 3.13.13 | Oct 7, 2024 | Oct 31, 2029 | 1271 days remaining | Active |
| 3.14 | 3.14.4 | Oct 7, 2025 | Oct 31, 2030 | 1636 days remaining | Active |
When a Python version 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 Python 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.
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Python versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Extended security support for Python beyond PSF EOL dates.
Learn More →Upload your dependency file and scan your entire stack for EOL risk in seconds. Free, no account required.
Stack Scanner →