{"id":2952,"date":"2026-11-05T09:52:42","date_gmt":"2026-11-05T09:52:42","guid":{"rendered":"https:\/\/hostry.com\/blog\/?p=2952"},"modified":"2026-11-05T09:52:44","modified_gmt":"2026-11-05T09:52:44","slug":"python-3-10-end-of-life-ubuntu-22-04","status":"publish","type":"post","link":"https:\/\/hostry.com\/blog\/python-3-10-end-of-life-ubuntu-22-04\/","title":{"rendered":"Python 3.10 End of Life: What It Means on an Ubuntu 22.04 VPS"},"content":{"rendered":"\n
\"Python<\/figure>\n\n\n\n
You run an Ubuntu 22.04 VPS, python3 --version prints Python 3.10.12, and a scanner or a library changelog now flags Python 3.10 end of life. The interpreter Ubuntu installed keeps getting Canonical security fixes until May 2027 (Ubuntu Pro stretches that to 2032), but upstream support ended on October 1, 2026, and your own virtualenvs and pip dependencies are the part that ages from here.<\/strong><\/em><\/pre>\n\n\n\n
That 3.10.12 does not mean ten missed releases. Canonical keeps the version string it shipped and backports fixes into it. What needs checking is each of your applications: where its interpreter comes from, and which pip dependencies it pins. On a Hostry KVM VPS<\/a><\/strong> you have root, so you run that check and the move to 3.12 yourself.<\/p>\n\n\n\n
Paths below such as \/srv\/app<\/span>, the user deploy<\/span> and the unit app.service<\/span> are placeholders for your own. On November 5, 2026, package versions and dates were checked against the Ubuntu archive and python.org. The uv commands ran with uv 0.13.7 on a clean Ubuntu test system, and the python3-minimal repair in a minimal 22.04 chroot.<\/p>\n\n\n\n
Python 3.10 end of life: what ended on October 1 and what did not<\/h2>\n\n\n\n
PEP 619, the Python 3.10 release schedule<\/a><\/strong>, promised source-only security releases until October 1, 2026, five years after 3.10.0. Python 3.10.22 came out that day and was the final one. The core team now accepts no 3.10 issues on the bug tracker, so a CPython flaw found in November is patched on 3.11 and newer and stays open on 3.10 upstream.<\/p>\n\n\n\n
Upstream, Python 3.10 is no longer supported in any form. The Python developer guide’s version table<\/a><\/strong> shows where the newer lines stand:<\/p>\n\n\n\n
Version<\/th>Upstream status (November 5, 2026)<\/th>Upstream end of life<\/th>Default python3 on<\/th><\/tr><\/thead>
3.10<\/td>End of life, last release 3.10.22<\/td>October 1, 2026<\/td>Ubuntu 22.04<\/td><\/tr>
3.11<\/td>Security fixes only<\/td>October 2027<\/td>None of the LTS releases<\/td><\/tr>
3.12<\/td>Security fixes only<\/td>October 2028<\/td>Ubuntu 24.04<\/td><\/tr>
3.13<\/td>Security fixes only<\/td>October 2029<\/td>None of the LTS releases<\/td><\/tr>
3.14<\/td>Bug fixes<\/td>October 2030<\/td>Ubuntu 26.04<\/td><\/tr>
3.15<\/td>Bug fixes, first released October 9, 2026<\/td>October 2031<\/td>None yet<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
The packaged \/usr\/bin\/python3.10<\/span> keeps receiving Canonical fixes through apt, as the patching breakdown below<\/a><\/strong> shows.<\/p>\n\n\n\n
Python 3.10 security updates on Ubuntu 22.04: who patches what<\/h2>\n\n\n\n
On 22.04, python3.10 lives in the main<\/strong> component. According to the Ubuntu release cycle page<\/a><\/strong>, packages in main get standard security maintenance on 22.04 until May 2027, and Expanded Security Maintenance through Ubuntu Pro runs to May 2032. Canonical is still doing that work. The current jammy-security build, 3.10.12-1~22.04.18<\/span>, reached the archive in September 2026 with fixes for CVE-2026-4360 in tarfile extraction and CVE-2026-15308 in the HTML parser.<\/p>\n\n\n\n
Those updates stop at the package itself. Everything else Python-related on the server is a separate installation or dependency to inspect:<\/p>\n\n\n\n