EOL Python Security Patches — Versions 2.7 Through 3.13

php2shell patches (CVE-2026-109618 and CVE-2026-109619) for EOL PHP are out now. With sales replies slower than usual due to high demand, the fastest route to patched packages is to buy ELS for Runtimes online (opens in new tab). Read the patch FAQ

 

2.7 to 3.X

Bridging legacy Python
versions to modern platforms

Software written in Python 2.7 or older Python 3 releases is hard to deploy on modern enterprise platforms in a compliant manner – either because these interpreters aren’t available in EL9‑class repositories and require additional work to support the newer OpenSSL and C runtime shipped in EL9 or because they no longer receive upstream security fixes. Yet these applications remain critical, and rewriting them for the latest Python versions can be time‑consuming or prohibitively expensive.

 

What can we do to help
with your application
transformation
journey?

Challenges with Backporting

Backporting unsupported Python versions takes deep expertise and experience. Clients who require this bridge need multiple layers of support, including continuous patching for current and future CVEs. TuxCare, a global leader in Linux and open‑source patching, delivers that protection so your applications run securely on modern enterprise platforms.

Capturing your technical needs today

TuxCare offers similar code bridge capabilities for PHP and other applications requiring extended support beyond the
manufacturers' lifecycles. Application teams need time to develop their next-gen code and communicate confidence with
their clients while having the ability to extend the life of their solution and maintain the highest security.

ELS from TuxCare buys you the time needed while providing the required updates to keep your
client secure during your application transformation.

Extend your timeline for development without rushing clients to upgrade prematurely.

Create a solid migration of code without jeopardizing client stability.

Continue to receive CVE updates well beyond the manufacturer's EOL date.

Partnering with TuxCare

Whether you need to keep critical applications on Python 2.7 or early Python 3 (3.3‑3.9) today or map your path
to the latest Python releases, TuxCare is the partner of choice. We provide the security bridge that lets you run legacy code
with confidence while you plan—and fund—future upgrades, all without disrupting your customer base.

Securely Moving Forward

Why should you change your code when a new version of a language is released if it runs fine as-is? Python Endless
Lifecycle Support from TuxCare breathes new life into code written for out-of-support Python versions with rapid security
updates, vulnerability fixes, and more.

Why TuxCare?

TuxCare makes enterprise Linux more secure, stable, and reliable at our core. We take care of Linux and other open-source frameworks so that organizations can comfortably and affordably use open-source software to support environments requiring high levels of cybersecurity, stability, and availability.

Learn more about what TuxCare’s Endless Lifecycle Support for Python can do for your organization.

Why TuxCare?

15 years of proven excellence in open-source patching have created highly
automated processes and systems, providing:

Extensive Coverage of Open-Source Technologies

We provide long-term security across your entire stack, supporting a wide and continually expanding set of open-source projects, libraries, and runtimes – all from a single, trusted partner.

Efficiencies in Build Chains and Testing

We utilize advanced automation across CVE discovery, backporting, building, and release workflows to accelerate delivery and ensure the highest possible quality of security patches.

Identification and Patching of Transitive Dependencies

We go beyond surface-level scanning to uncover and fix hidden vulnerabilities deep in your dependency trees, securing the entire software supply chain with precision and scale.

Fast and Consistent Delivery of Patches with Supporting SLAs

Automated pipelines and mature workflows ensure rapid, reliable patch delivery backed by SLAs – giving you confidence in your risk management and compliance posture.

We’ve Been Powering Enterprise-Grade Patching At
Unprecedented Scale – and We're Just Getting Started

2,700+
Enterprise Clients

70,000+Packages Curated

420,000+
Patches Delivered

14,000+
Vulnerabilities Fixed

11,000+
Kernels Supported

70+
Linux Distro Versions Supported

Frequently Asked Questions

ELS for Python delivers security fixes for Python interpreter versions that have reached end of life upstream. TuxCare ships patched builds called alt-python, which install alongside the system Python under /opt/alt/, so you can keep running apps on Python 2.7 or an older 3.x release while TuxCare continues to fix security issues in the interpreter.

Python 2.7 and 3.6 through 3.14, depending on the operating system. Every version is available on EL 7, 8, 9 and 10, on Ubuntu 18.04, 20.04 and 22.04, and on Debian 12 and 13, with slightly narrower sets on Ubuntu 16.04 and 24.04, Debian 10 and 11. Alpine 3.23 and 3.24 get Python 3.6 through 3.9. The full matrix is on docs.tuxcare.com.

Yes. Python 3.10 reached its upstream end of life in October 2026, following Python 3.9 in October 2025 and 3.8 in October 2024. After that point, CPython stops shipping security fixes for the line. ELS for Python keeps patching those versions, along with 2.7, 3.6 and 3.7, so apps pinned to them stay secure and compliant.

Yes. Every alt-python package ships its own bundled pip, setuptools and wheel, and those are covered by ELS and patched together with the interpreter. That matters because packaging tools carry their own CVEs, and scanners flag them just as readily as the interpreter itself.

That's exactly how alt-python is designed. Each version installs into its own directory under /opt/alt/, so a legacy app can stay on 3.6 while newer services run 3.12 on the same host. Nothing replaces or overwrites the operating system's default Python.

TuxCare targets 14 days from public disclosure for critical and high vulnerabilities (CVSS 7.0 and above), 60 days for medium and 90 days for low. Reported issues get an initial response within three days, and TuxCare publishes VEX for runtimes as part of its CSAF advisory feed, which compatible scanners can use to see what's actually fixed.

The interpreter is only half the picture. TuxCare also maintains patched versions of widely used Python libraries, including requests, urllib3, cryptography, Jinja2, Flask and FastAPI, delivered through a TuxCare-managed PyPI-compatible index. Pairing the runtime with library coverage addresses findings in requirements.txt as well as in the interpreter.

Talk to a TuxCare Expert

Tell us your challenges and our experts will help you find the best approach
to address them with the TuxCare product line.

Long-Term Security After Standard Support Ends

TuxCare ELS continues to deliver enduring security for your distro, language, or software development framework for as many years as your organization requires