Python 3.9 end of life
Python 3.9 reached end of life on 31 October 2025, and 3.9.25, released that day, was its last release. The Python project has shipped no fix for the 3.9 branch since. You can upgrade to 3.12 or 3.13, or keep 3.9 patched: OSSeva patches Python 3.9 after end of life.
What now
Which vendors provide Python 3.9 security patches now that support has ended?
Python Extended Support: Security Patches for 3.9 and 3.10- End of life
- 31 October 2025
- Released
- Oct 2020
- Final release
- 3.9.25
- Successor
- Python 3.12 or 3.13
Date published by Python developer guide: versions. We do not publish a lifecycle date we cannot source. Dates checked on the Python developer guide, python.org and endoflife.date on 19 November 2026.
Last reviewed
Python versions: release and end-of-life dates
| Version | Released | End of life | Status |
|---|---|---|---|
| Python 3.11 | 24 Oct 2022 | October 2027 | Approaching |
| Python 3.10 | 4 Oct 2021 | 1 October 2026 | End of life |
| Python 3.9 (this page) | 5 Oct 2020 | 31 October 2025 | End of life |
| Python 3.8 | 14 Oct 2019 | 7 October 2024 | End of life |
End-of-life dates are published by each project and checked against endoflife.date.
What actually stops on 31 October 2025
- Security fixes on the 3.9 branch. 3.9.25 (31 October 2025) is the last release, and python.org lists no later 3.9 build.
- Source releases of 3.9. Bug fixes had already ended on 17 May 2022.
- Triage of new reports against 3.9. A vulnerability found after 31 October 2025 is fixed in the supported lines only.
What actually breaks in the upgrade
Which Python line to move to
The Python developer guide lists 3.11 until October 2027, 3.12 until October 2028 and 3.13 until October 2029. From 3.9, 3.12 or 3.13 gives the longest run for the work involved. Python 3.10 is already end of life too, so it is not a useful stop. Python developer guide: versions.
The language gap is small, the library gap is not
NumPy 2.1.0 needs Python 3.10 or newer and pandas 3.0.0 needs 3.11 or newer, so a 3.9 environment sits on NumPy 2.0 and pandas 2.3 at most. Compiled packages are usually what turns a minor version bump into a project.
Check the OpenSSL version on the host
Python 3.10 and later require OpenSSL 1.1.1 or newer. A 3.9 host that still links an older OpenSSL cannot take the upgrade until the base image changes as well.
Python 3.9 dates and releases
Each date is from the Python developer guide and endoflife.date, and the last release from python.org, read on 19 November 2026.
| Milestone | Date | Source |
|---|---|---|
| First release (3.9.0) | 5 Oct 2020 | Python developer guide |
| Bug fixes ended | 17 May 2022 | endoflife.date |
| End of life, and last release 3.9.25 | 31 Oct 2025 | Python developer guide; python.org release API |
| Python 3.10 end of life | 1 Oct 2026 | Python developer guide |
| Python 3.11 end of life | Oct 2027 | Python developer guide |
What is specific to Python 3.9
Python 3.9 gave the language dict union operators (PEP 584), str.removeprefix and removesuffix, generics on the standard collections such as list[int] (PEP 585), the zoneinfo module and a new PEG parser (PEP 617). It does not have match statements or the X | Y union syntax, which arrived in 3.10, so annotations that use them cannot run on 3.9.
It is also the line where Windows 7 support stopped. The Python 3.9 documentation states that 3.9 supports Windows 8.1 and newer and tells anyone who needs Windows 7 to install Python 3.8. An estate that still has Windows 7 desktops cannot move those to 3.9 or later at all.
Library floors have passed it. In PyPI metadata, NumPy 2.1.0 (18 August 2024) requires Python 3.10 or newer and pandas 3.0.0 (21 January 2026) requires 3.11 or newer. NumPy 2.0.2 (26 August 2024) and pandas 2.3.3 (29 September 2025) still declare 3.9, so they are the newest releases a 3.9 environment can take. Anything that has pinned a newer series will not resolve. The last release, 3.9.25, appeared on 31 October 2025, the same day as the end-of-life date, so unlike 3.8 there was no gap between the final build and the cutoff.
The move off 3.9 crosses specific removals. 3.10 removed the old-parser parser module, which 3.9 had deprecated, and 3.11 removed binhex, also deprecated in 3.9. 3.12 then removed distutils, asyncore, asynchat, imp and smtpd. A project that never ran with DeprecationWarning visible on 3.9 should do so before choosing a target, because the warnings it has been ignoring become import errors on the way up.
Sources: docs.python.org/3.9/whatsnew and using/windows, 3.10, 3.11 and 3.12 whatsnew; pypi.org JSON metadata for numpy and pandas. All read on 19 November 2026. We list no CVEs on this page because we could not cross-check a CVE record and a vendor advisory that both name the 3.9 line.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Upgrade to Python 3.12 or 3.13 | Move to a line with security fixes until October 2028 (3.12) or October 2029 (3.13). | Scales with dependencies, compiled extensions and test coverage | Engineering time | The default destination. |
| Extended security support | Backported fixes for Python 3.9: Critical CVEs within 48 hours, High within 7 days. | Starts from your current version | Subscription, priced per application | For services held by a dependency, a vendor certification or a release freeze. |
| Stay unpatched | No fixes for vulnerabilities found since 31 October 2025. | None | Zero now | A year of unfixed releases has already passed. Hard to defend in a scanned environment. |
What OSSeva does for Python 3.9
OSSeva patches this line
OSSeva patches Python 3.9 after end of life, and also Python 3.8, 3.10 and, once upstream stops in October 2027, 3.11. Other versions are assessed case by case through a version coverage check.
Python extended supportWhat your auditor will say
Requirement 6.3.3. Payment pages and APIs on an unsupported runtime need patched components or a documented compensating control.
CC7.1. Auditors look for evidence that production runtimes receive security fixes.
Is Python 3.9 end of life?
Yes. Python 3.9 reached end of life on 31 October 2025 per the Python developer guide, and its last release was 3.9.25.
What was the last Python 3.9 release?
3.9.25, released on 31 October 2025 according to python.org.
Is Python 3.9 still safe to use?
It runs, but the Python project has issued no security fix for it since 31 October 2025, so new vulnerabilities stay open unless a third party patches them.
Should I upgrade Python 3.9 to 3.12 or 3.13?
3.13 if your dependencies support it: it has security support until October 2029. 3.12 is supported until October 2028. 3.10 has already ended.
Can I get security patches for Python 3.9 after end of life?
Yes. OSSeva patches Python 3.9 after end of life. Pricing is per application, and other Python versions are assessed through a version coverage check.
Does Python 3.9 run on Windows 7?
No. The Python 3.9 documentation says 3.9 supports Windows 8.1 and newer and tells Windows 7 users to install Python 3.8.
Get a quote
Still running Python 3.9?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.
Prefer to talk or read more first?