Python

Python End of Life — All Versions & Security Risk

Last updated 27 June 2026

17

Versions tracked

12

At EOL

5

Supported

Python version lifecycle and end-of-life dates
Version Released Active Support Security Support Status Latest
Python 3.14
07 Oct 2025
01 Oct 2027 Ends in 1 year, 3 months
31 Oct 2030 Ends in 4 years, 4 months
Active 3.14.6
Python 3.13
07 Oct 2024
01 Oct 2026 Ends in 3 months
31 Oct 2029 Ends in 3 years, 4 months
Active 3.13.14
Python 3.12
02 Oct 2023
02 Apr 2025 Ended 1 year, 2 months ago
31 Oct 2028 Ends in 2 years, 4 months
Active 3.12.13
Python 3.11
24 Oct 2022
01 Apr 2024 Ended 2 years, 2 months ago
31 Oct 2027 Ends in 1 year, 4 months
Active 3.11.15
Python 3.10
04 Oct 2021
05 Apr 2023 Ended 3 years, 2 months ago
31 Oct 2026 Ends in 4 months
Active 3.10.20
Python 3.9
05 Oct 2020
17 May 2022 Ended 4 years, 1 month ago
31 Oct 2025 Ended 7 months, 3 weeks ago
EOL 3.9.25
Python 3.8
14 Oct 2019
03 May 2021 Ended 5 years, 1 month ago
07 Oct 2024 Ended 1 year, 8 months ago
EOL 3.8.20
Python 3.7
27 Jun 2018
27 Jun 2020 Ended 6 years ago
27 Jun 2023 Ended 3 years ago
EOL 3.7.17

What is Python's end-of-life policy?

Python follows a 5-year support lifecycle from the initial release date — 2 years of full support with bug fixes and security patches, followed by 3 years of security-only fixes. After the security support window ends, no further patches are released by the Python Software Foundation. A new major Python version is released each October.

Which Python versions are currently supported?

As of 2026, the actively supported Python versions are 3.10, 3.11, 3.12, 3.13, and 3.14. Python 3.9 reached its security-only phase and ends in October 2025. Python 3.8 and earlier have reached end of life and receive no official security patches.

What happens when a Python version reaches end of life?

Once a Python version reaches end of life, the Python Software Foundation stops releasing security updates entirely. Any new vulnerabilities discovered after the EOL date will remain unpatched on that version. Organizations running EOL Python face compounding security risk as CVEs accumulate with no remediation path from upstream.

Does running EOL Python affect PCI-DSS compliance?

Yes. PCI-DSS 4.0 Requirement 6.3.3 requires all system components to be protected from known vulnerabilities via applicable security patches. EOL software fails this requirement by definition since no patches are available. Auditors will flag EOL Python as a finding during PCI-DSS assessments.

Can I get security patches for EOL Python versions?

Yes — commercial extended lifecycle support vendors provide security patches for EOL Python versions. This is a bridge option for organizations that cannot immediately migrate. Migration to a supported Python version (3.11 or 3.12 recommended) remains the long-term solution.

How do I check which Python version I am running?

Run the following command in your terminal:

python --version

or

python3 --version