Python 3.10 end of life
Python 3.10 reached end of life on 1 October 2026, and 3.10.22, released the same day, is its last release. The Python project makes no further changes to the 3.10 branch, including security fixes. You can upgrade to 3.12 or 3.13, or keep 3.10 patched: OSSeva patches Python 3.10 after end of life.
What now
Which vendors provide Python 3.10 security patches now that support has ended?
Python Extended Support: Security Patches for 3.9 and 3.10- End of life
- 1 October 2026
- Released
- Oct 2021
- Final release
- 3.10.22
- 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 (this page) | 4 Oct 2021 | 1 October 2026 | End of life |
| Python 3.9 | 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 1 October 2026
- Security fixes on the 3.10 branch. 3.10.22 (1 October 2026) is the last release, and python.org lists no later 3.10 build.
- Source releases of 3.10. Python 3.10 had already stopped getting bug fixes on 5 April 2023, so it spent its last three and a half years on security-only releases.
- Triage of new reports against 3.10. A flaw found later 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, 3.13 until October 2029 and 3.14 until October 2030. 3.12 is the smallest step that gives more than a year of support. Check that your frameworks and compiled packages publish wheels for the target before you start. Python developer guide: versions.
Libraries are leaving 3.10
NumPy 2.3.0 and pandas 3.0.0 declare Python 3.11 or newer in their PyPI metadata, so a 3.10 environment cannot take new releases of either. The longer 3.10 stays, the more of the dependency tree is pinned to old releases.
Run the suite on 3.11 and 3.12 with warnings on
Python 3.11 removed the binhex module and @asyncio.coroutine, and 3.12 removed distutils, asyncore, asynchat, imp and smtpd. Code that still imports them fails on the new interpreter, not on 3.10.
Python 3.10 dates and releases
Each date is from the Python developer guide and endoflife.date, and each release date from python.org, all read on 19 November 2026.
| Milestone | Date | Source |
|---|---|---|
| First release (3.10.0) | 4 Oct 2021 | Python developer guide |
| Bug fixes ended | 5 Apr 2023 | endoflife.date |
| 3.10.21 | 12 Aug 2026 | python.org release API |
| End of life, and last release 3.10.22 | 1 Oct 2026 | Python developer guide; python.org release API |
| Python 3.11 end of life | Oct 2027 | Python developer guide |
| Python 3.12 end of life | Oct 2028 | Python developer guide |
What is specific to Python 3.10
Python 3.10 added structural pattern matching (PEP 634), the X | Y union type syntax (PEP 604) and officially allowed parenthesized context managers, per its release notes. A codebase that uses match statements does not parse on 3.9 or earlier, so a 3.10 service can only move forward, never back to an older interpreter.
3.10 is also where the ssl module began to require OpenSSL 1.1.1 or newer (PEP 644). Python 3.10 does not support OpenSSL 1.0.2. A host or image that carries Python 3.10 therefore also carries OpenSSL 1.1.1 or later, and keeping that library patched is a separate task from patching the interpreter.
Ubuntu 22.04 ships 3.10 as its system python3: packages.ubuntu.com lists python3 3.10.6-1~22.04 for jammy, read on 19 November 2026. That interpreter is built by Ubuntu, so a scan of the system Python and a scan of a python.org 3.10.22 build in a container can report different findings. Find out which one your application runs on before you read the scan.
Libraries have started to leave 3.10. The PyPI metadata for NumPy 2.3.0 (7 June 2025) and pandas 3.0.0 (21 January 2026) both say Python 3.11 or newer. A 3.10 environment stays on earlier series of each, so every later fix in those packages needs an interpreter upgrade first.
The way up is not free of removals. Python 3.11 removed the binhex module and the @asyncio.coroutine decorator, and 3.12 removed distutils (PEP 632, which setuptools can still provide), asyncore, asynchat, imp and smtpd. Run the test suite on 3.11 and 3.12 with warnings enabled and pick the target from the result.
Sources: docs.python.org/3.10/whatsnew, 3.11/whatsnew and 3.12/whatsnew; pypi.org JSON metadata for numpy and pandas; packages.ubuntu.com. 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.10 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. |
| Upgrade to Python 3.11 | The smallest step from 3.10. | Scales with test coverage | Engineering time | An interim step. 3.11 ends in October 2027. |
| Extended security support | Backported fixes for Python 3.10: 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 newly found vulnerabilities in the interpreter or standard library. | None | Zero now | Python services often sit behind public APIs. A poor place to carry risk. |
What OSSeva does for Python 3.10
OSSeva patches this line
OSSeva patches Python 3.10 after end of life, and also Python 3.8, 3.9 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.10 end of life?
Yes. Python 3.10 reached end of life on 1 October 2026 per the Python developer guide, and its last release is 3.10.22.
What was the last Python 3.10 release?
3.10.22, released on 1 October 2026 according to python.org. 3.10.21 came on 12 August 2026.
Is Python 3.10 still safe to use?
It runs, but it no longer receives security fixes from the Python project, so new vulnerabilities in the interpreter and standard library stay open unless a third party patches them.
Should I upgrade Python 3.10 to 3.12 or 3.13?
3.13 if your dependencies support it: it has security support until October 2029. 3.12 is the smaller step and is supported until October 2028.
Can I get security patches for Python 3.10 after end of life?
Yes. OSSeva patches Python 3.10 after end of life. Pricing is per application, and other Python versions are assessed through a version coverage check.
Does Ubuntu 22.04 still get Python 3.10 fixes?
The system python3 on Ubuntu 22.04 is built and updated by Ubuntu, not by the Python project, so its patching follows Ubuntu's own security notices. A python.org or container build of 3.10 has no such source.
Get a quote
Still running Python 3.10?
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?