// Python extended support
Python extended support: security patches for 3.9 and 3.10.
Keep the interpreter you run patched after the Python project stops.
OSSeva provides Python security patches for versions 3.9 and 3.10 after the Python project stopped fixing them. Critical CVEs (CVSS 9.0 or higher) are fixed within 48 hours and High within 7 days. Priced per application runtime, and a senior engineer replies within 1 business day with a quote. Python 3.9 reached end of life on 31 October 2025 and Python 3.10 on 1 October 2026. Other Python versions are assessed case by case. Upgrading is usually the better move; extended support is for services held back by a dependency, a vendor certification or a release freeze.
- Covered versions
- 3.9, 3.10
- Critical CVEs
- Fixed in 48 hours
- High CVEs
- Fixed in 7 days
- Python 3.11 ends
- October 2027
Dates checked 17 November 2026 against the Python developer guide (devguide.python.org/versions) and endoflife.date.
Trusted globally by enterprises





Why Python 3.9 and 3.10 are still in production
Most Python upgrades are a dependency bump and a test run. These are the reasons some services stay on an ended line.
End of life means new flaws stay open
The Python developer guide says an end-of-life release is frozen and allows no further changes. A vulnerability found in 3.9 or 3.10 now is fixed only in the supported lines.
Dependencies and certifications decide the date
A compiled extension, a vendor-certified platform or a pinned base image can hold a service on one Python version. The date to move is then set by that dependency, not by the Python calendar.
Python 3.11 is a short stop
The developer guide lists Python 3.11 as security-fixes-only with end of life in October 2027, and 3.12 in October 2028. A move from 3.10 to 3.11 means another upgrade within a year.
The dates that matter
2025-10-31
Python 3.9 reaches end of life.
2026-10-01
Python 3.10 reaches end of life.
What OSSeva delivers
Patched Python 3.9 and 3.10
Security fixes backported to the Python 3.9 or 3.10 you run, signed. Critical CVEs within 48 hours, High within 7 days. You keep your interpreter version.
Compliance documents and an upgrade plan
A SOC 2 and HIPAA attestation package, 24/7 reactive support and an assessment of the upgrade path to a supported Python line.
Python operated
24/7 application and runtime monitoring, a 15-minute P1 incident response SLA and a named senior engineer on your account.
Your options, compared
| Option | What you get | Trade-off |
|---|---|---|
| Upgrade to a supported Python | A line the project still fixes: 3.11 to October 2027, 3.12 to October 2028, with 3.13 and later beyond | Dependencies and compiled extensions to retest. For most services this is the right answer. |
| Third-party Python support | Fixes for ended lines from providers such as TuxCare, whose page lists Python versions and fix targets | Version lists can depend on the operating system; confirm yours with the provider. |
| OSSeva extended support | Patched 3.9 and 3.10 with a stated patch SLA, on one contract with the rest of your stack | A subscription priced per application runtime, for as long as you stay. Other Python versions are assessed case by case. |
| Stay unpatched | Nothing | Python services are often internet-facing, and every new fix in the supported lines adds findings you cannot close. |
Dates from the Python developer guide (devguide.python.org/versions), cross-checked with endoflife.date on 17 November 2026. Patch SLA and coverage from the OSSeva Python technology page.
Which Python versions does OSSeva cover?
Python 3.9 and 3.10 after end of life. Other versions are assessed case by case.
How quickly are Python vulnerabilities patched?
Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.
Is Python 3.10 end of life?
Yes. The Python developer guide lists 3.10 as end-of-life with a date of 1 October 2026.
Is Python 3.9 end of life?
Yes. Python 3.9 reached end of life on 31 October 2025.
What does Python extended support cost?
It is priced per application runtime, as the pricing page explains. A senior engineer replies within 1 business day with a quote.
Get a quote
Upgrade what you can.
Patch what you cannot.
Book a discovery call with your Python versions and dependencies, and we will send a quote priced per application runtime.
Prefer to talk or read more first?