Ubuntu 22.04 End of Life (EOL): May 2027, What Changes and What to Do
Canonical's free security updates for Ubuntu 22.04 LTS end in May 2027. Machines keep running, CI runners and platforms drop it sooner, and only Ubuntu Pro patches it after.
Written Shahzeb Umer
SubscribeStatus
SupportedLTS
Support ends .
- Time left
- 194 days
- Latest release
- 22.04.5
- Move to
- Ubuntu 26.04fixed until 29 May 2031
5.1 years of support
- Bug and security fixes21 Apr 2022 – 30 Sep 2024
- Security fixes only30 Sep 2024 – 1 Jun 2027
Supported for 5.1 years, from 21 Apr 2022 to 1 Jun 2027.
Who still patches it
Six places Ubuntu 22.04 runs, five deadlines.
- Ubuntu 22.04 (Canonical, Main): Ubuntu Pro to May 2032
- GitHub Actions, Azure Pipelines (ubuntu-22.04): Removed 17 Apr 2027
- AWS Deep Learning AMIs (Ubuntu 22.04): Patches end 30 Apr 2027
- Heroku (heroku-22 stack): End of life 30 Apr 2027
- Azure AKS (Ubuntu 22.04 node images): Images removed 30 Apr 2028
- Docker image (ubuntu:22.04): Still rebuilt, no end announced
Where to move
Be on Ubuntu 26.04.
The short version
- Ubuntu 22.04 LTS's standard security maintenance ends in May 2027, Canonical says. It has not named the day yet, and distro-info-data lists 1 June 2027. After that only Ubuntu Pro brings security updates, until May 2032. Pro is free for personal use on up to five machines, and $500 a year per server otherwise.
- Platforms leave first. GitHub Actions and Azure Pipelines remove
ubuntu-22.04on 17 April 2027 after brownouts from 23 March, Heroku-22 reaches end of life on 30 April 2027, and AKS stops patching 22.04 nodes on 30 June 2027. - Move to Ubuntu 26.04 LTS, supported until May 2031. In place that takes two upgrades, through 24.04. Anything you rebuild, such as container images and CI jobs, can go straight there.
On this page
Ubuntu 22.04 LTS reaches the end of standard security maintenance in May 2027, the month Canonical's release cycle page gives. After that, Canonical publishes security updates for 22.04 only to machines attached to Ubuntu Pro, which covers it until May 2032. Nothing on the machine checks the date: a 22.04 server boots, runs and installs packages the same way in June 2027 as it did in May.
What changes is who still patches it, and who still runs it for you. Several platforms leave before Canonical does, and one has started.
What stops in May 2027
For five years, Canonical publishes free CVE fixes for the packages in Main, about 2,300 per release, including the kernel, OpenSSL, OpenSSH and Python 3.10. Universe, the community repository of more than 36,000 packages, never had that commitment. The most recent point release, 22.04.5, came out on 12 September 2024. The release notes gave the other official flavours, such as Kubuntu and Xubuntu, three years rather than five.
When standard maintenance ends, fixes continue only through Expanded Security Maintenance (ESM) in Ubuntu Pro. ESM covers Main and Universe until May 2032, with what Canonical calls "critical and high security patches". The Legacy add-on, bought separately, adds five more years, to May 2037.
The exact day is not settled yet. The sources disagree:
- Canonical's release cycle page: May 2027.
- The 22.04 release notes: "5 years until April 2027".
- distro-info-data, the release table Ubuntu's own tools read: 1 June 2027. endoflife.date uses the same date, and so does the status box at the top of this page.
- Heroku says Canonical's standard support "ends on April 30th, 2027".
For 20.04, Canonical named the day six weeks ahead: on 17 April 2025 it announced that 20.04 would move to ESM on 29 May 2025. Expect a similar notice for 22.04 in spring 2027, and plan for the free updates to stop at the end of May. The ESM end differs the same way: May 2032 on the release cycle page, 21 April 2032 in distro-info-data.
Who still runs or patches Ubuntu 22.04
| Where it runs | Until | What happens after | Source |
|---|---|---|---|
| Canonical, packages in Main | May 2027, free | Security updates only with Ubuntu Pro | Release cycle |
| Ubuntu Pro (ESM), Main and Universe | May 2032 | Legacy add-on to May 2037, at 50% more than Pro | Release cycle, pricing |
GitHub Actions and Azure Pipelines, ubuntu-22.04 and ubuntu-22.04-arm |
Deprecated since 17 September 2026 | Brownouts from 23 March 2027, removed 17 April 2027 | runner-images #14254, Azure DevOps |
| AWS Deep Learning AMIs, Ubuntu 22.04 and Ubuntu Pro 22.04 | End of patch 30 April 2027 | No further patches | DLAMI policy |
Heroku, heroku-22 stack |
End of life 30 April 2027 | No builds from 1 May 2027; running apps are not shut down | Heroku |
| Azure AKS, Ubuntu 22.04 node images | 30 June 2027 | No new node pools, node images or patches; images removed 30 April 2028 | AKS node images |
| Amazon EKS, Canonical's Ubuntu AMIs | 22.04 images (Ubuntu Pro) for Kubernetes 1.31 to 1.34 only | 24.04 and 26.04 images for newer versions | Canonical EKS AMIs |
| Google GKE, Ubuntu node image | Default moved to 24.04 from GKE 1.32.1-gke.1002000 | No 22.04 end date published | GKE release notes |
CircleCI, ubuntu-2204 machine image |
Supported | CircleCI aims to start removal "within 3 months of Canonical's EOL date" | CircleCI |
Docker official image ubuntu:22.04 |
Still rebuilt: jammy-20261110, pushed 12 November 2026 |
Not announced. 20.04 left the image on 1 June 2025 | official-images |
Python 3.10 shows how distribution support works. python.org stopped fixing 3.10 on 1 October 2026, with 3.10.22. Ubuntu's python3.10 package is in Main and still patched: version 3.10.12-1~22.04.18, published on 8 September 2026, fixed CVE-2026-4360 in tarfile and CVE-2026-15308 in the HTML parser. python3 --version still prints 3.10.12, because Canonical backports fixes instead of moving to new upstream releases; apt changelog python3.10 shows what is in. That continues until May 2027, and with Ubuntu Pro until May 2032. A pyenv build, a python:3.10 image or an interpreter you compiled gets nothing. The Python 3.10 page covers those.
Universe is the gap. Canonical's free commitment covers Main only. On 22.04, Node.js 12 and docker.io are Universe packages, and they get Canonical's security commitment only through Ubuntu Pro.
What breaks first
Nothing fails on a fixed day in May. The consequences arrive on other people's schedules, and some have started.
Heroku builds are already failing. Since 1 November 2026, the first build of each Heroku-22 app in a 30-day period fails with a deprecation error. From 1 February 2027 that happens every 7 days, from 1 April every 24 hours, and from 1 May 2027 no builds or new Heroku-22 apps are allowed.
CI next, from 23 March 2027. GitHub and Azure fail every ubuntu-22.04 job during four brownouts, on 23 and 30 March and 6 and 13 April 2027, each from 14:00 UTC to midnight. From 17 April those jobs are "terminated with an error". Self-hosted runners are not affected. Separately, ubuntu-latest moves from 24.04 to 26.04 by 19 November 2026, so unpinned workflows change release this month.
Vendor repositories follow Canonical's date. When 20.04 ended, Docker Engine 28.2.0 (28 May 2025) dropped its focal packages "as it reached end of life", PostgreSQL's apt repository removed focal on 31 July 2025, and the deadsnakes PPA deletes packages "once a distribution version reaches end-of-life". Microsoft says .NET is no longer supported on an Ubuntu version that "falls out of support", NVIDIA supports each OS in CUDA until its "standard EOSS/EOL date", and ROS 2 Humble, built for 22.04, ends in May 2027. All of them still support 22.04 today. Ubuntu Pro patches Ubuntu's packages, not theirs.
Container images freeze. Docker's official ubuntu image dropped 20.04 in its first update after standard support ended, on 1 June 2025, and its last 20.04 build dated from 4 April. Old tags still pull, but are never rebuilt.
Scanner findings, from 1 June 2027. Tenable's Nessus plugin 201473, Canonical Ubuntu Linux SEoL (22.04.x), carries an end date of 1 June 2027, and Tenable says these plugins report only once that date is reached. It is rated Low today, while the 20.04 plugin, past its date, is rated Critical. Neither plugin mentions Ubuntu Pro or ESM.
How to check what you run
On the machine:
lsb_release -ds # Ubuntu 22.04.5 LTS
grep -E '^(VERSION_ID|VERSION_CODENAME)=' /etc/os-release
grep '^22.04' /usr/share/distro-info/ubuntu.csv # the dates Ubuntu's own tools use
pro status # is Ubuntu Pro attached, which services are on
pro security-status # installed packages from Main, Universe and third parties
After the end date, on a machine without Pro, pro security-status says it is "NOT receiving security patches because the LTS period has ended and esm-infra is not enabled".
In your repositories and on your hosts:
grep -rnE --include='Dockerfile*' --include='Containerfile*' 'FROM .*ubuntu:(22\.04|jammy)' .
grep -rn 'ubuntu-22.04' .github/workflows/ azure-pipelines*.yml
docker ps --format '{{.Names}}\t{{.Image}}' | grep -E 'ubuntu:(22\.04|jammy)'
docker run --rm <image> cat /etc/os-release # images built on 22.04 without saying so
Across a fleet:
# Kubernetes nodes on any provider: OS-IMAGE shows "Ubuntu 22.04.5 LTS"
kubectl get nodes -o wide
# AWS instances managed by Systems Manager, once per region
aws ssm describe-instance-information \
--query "InstanceInformationList[].[InstanceId,PlatformName,PlatformVersion]" --output table
# Azure VMs: 22.04's image offer is 0001-com-ubuntu-server-jammy
az vm list --query "[].{name:name, offer:storageProfile.imageReference.offer, sku:storageProfile.imageReference.sku}" -o table
# AKS node pools: Ubuntu2204, or Ubuntu on Kubernetes 1.34 and older, means 22.04
az aks nodepool list -g RESOURCE_GROUP --cluster-name CLUSTER \
--query "[].{name:name, osSku:osSku, k8s:orchestratorVersion, image:nodeImageVersion}" -o table
Which version to move to: 26.04 LTS
| 22.04 LTS | 24.04 LTS | 26.04 LTS | |
|---|---|---|---|
| Standard security maintenance | May 2027 | May 2029 | May 2031 |
| Ubuntu Pro (ESM) | May 2032 | May 2034 | May 2036 |
| Python | 3.10 | 3.12 | 3.14 |
| OpenSSL | 3.0.2 | 3.0.13 | 3.5.5 |
| PostgreSQL | 14 | 16 | 18 |
| PHP | 8.1 | 8.3 | 8.5 |
OpenJDK (default-jdk) |
11 | 21 | 25 |
| Kernel (GA) | 5.15 | 6.8 | 7.0 |
| systemd | 249 | 255 | 259 |
| glibc | 2.35 | 2.39 | 2.43 |
Target Ubuntu 26.04 LTS. Its standard maintenance runs until May 2031, two years longer than 24.04's. It has had its first point release, 26.04.1, and Canonical has offered upgrades from 24.04 since 29 September 2026. The platforms are ready: GitHub made ubuntu-26.04 generally available on 17 September 2026, ubuntu:latest on Docker Hub is 26.04, and Heroku-26 is supported until April 2031.
In place, it takes two upgrades. Ubuntu upgrades an LTS release only to the next one. The release cycle page lists 24.04 as the only upgrade path from 22.04, and Ubuntu's server guide says you cannot skip releases. A 22.04 machine goes to 24.04 first, then to 26.04.
The skip rule. Anything you rebuild rather than upgrade, such as container images, CI jobs, autoscaled nodes and instances launched from an image, goes straight to 26.04. A long-lived machine passes through 24.04 on its way. Stop at 24.04 only if something you rely on is not ready for 26.04, such as a vendor repository with no 26.04 build or a host still booted with cgroup v1, and expect to be back here before May 2029.
How to upgrade
Buy time first, if you need it. Attaching a machine to Ubuntu Pro keeps Main patched after May 2027 and covers Universe now. By default, attaching turns on esm-infra, esm-apps and Livepatch:
sudo pro attach # prints a code to enter at ubuntu.com/pro/attach
pro status
Upgrade in place, twice. Ubuntu's server guide asks for a fully updated system before a release upgrade:
sudo apt update
sudo apt dist-upgrade -o APT::Get::Always-Include-Phased-Updates=true
[ -f /run/reboot-required ] && sudo reboot
sudo do-release-upgrade # 22.04 to 24.04; reboot, check, then run it again for 26.04
The upgrader disables third-party repositories and PPAs. Their software stays installed, and you re-enable each source once its vendor supports the new release. At configuration file prompts, the default keeps your version, so look at the differences before answering. Before the second upgrade, run stat -fc %T /sys/fs/cgroup/. cgroup2fs means cgroup v2; 26.04 refuses to upgrade a machine still on cgroup v1.
Databases need their own step. Each PostgreSQL major version is a separate package, postgresql-14 on 22.04 and postgresql-18 on 26.04, and pg_upgradecluster moves a cluster between them. The PostgreSQL 14 page covers that upgrade.
Rebuild where you can. Change FROM ubuntu:22.04 to FROM ubuntu:26.04 and runs-on: ubuntu-22.04 to ubuntu-26.04, and point launch templates and node pools at 26.04 images. A rebuild or fresh install is the only way to skip 24.04, and it lets you test before the new release carries traffic.
Changes most likely to bite between 22.04 and 26.04
1. pip install outside a virtual environment fails (24.04). High. From 24.04, Ubuntu's Python ships PEP 668's EXTERNALLY-MANAGED marker, and pip stops with error: externally-managed-environment. Scripts and Dockerfiles that pip install into the system Python break. Use a virtual environment, pipx for tools, or apt install python3-<name>.
2. Python 3.10 becomes 3.14 (24.04 and 26.04). High. Python 3.12 removed distutils, and 3.13 removed the "dead batteries" modules, including cgi, crypt and telnetlib. Run your test suite on 3.14 before the upgrade.
3. apt-key is gone (26.04). High. APT 3 removed the command, so install scripts that run apt-key add fail; the apt-secure(8) manual page explains managing keys directly. Since 24.04, Ubuntu's own sources live in /etc/apt/sources.list.d/ubuntu.sources in deb822 format instead of /etc/apt/sources.list, and APT requires repository keys of at least 2048-bit RSA, or Ed25519 or Ed448.
4. Server software jumps two major versions. High, if you run it. PostgreSQL 14 becomes 18, PHP 8.1 becomes 8.5, MySQL 8.0 becomes 8.4 and the default OpenJDK 11 becomes 25. Package names change with the version (php8.1-fpm becomes php8.5-fpm), so anything that names them needs updating.
5. cgroup v1 is gone (26.04). Medium. systemd 259 no longer supports it. A machine booted with cgroup v1 cannot upgrade to 26.04, and 26.04 containers will not run on a cgroup v1 host. 22.04 already defaults to cgroup v2, so this hits hosts switched back to v1 and older hosts, such as Ubuntu releases before 21.10, that run 26.04 images.
6. sudo and coreutils are Rust rewrites (26.04). Medium. sudo is now sudo-rs, the original is available as sudo.ws, and sudo-ldap was removed. The core utilities come from rust-coreutils, which Canonical says are "not fully compatible yet": cp, mv and rm stay GNU, and GNU versions remain under a gnu prefix, such as gnuls. Test scripts that depend on exact GNU behaviour or output.
7. Unprivileged user namespaces are restricted (24.04). Medium. AppArmor now limits unprivileged, unconfined programs that create user namespaces, which affects application sandboxes such as Chrome's and some container workloads. The 24.04 release notes give the fixes: an AppArmor profile that grants userns, or the kernel.apparmor_restrict_unprivileged_userns=0 sysctl, which gives up the protection.
8. /tmp is a tmpfs (from 24.10). Low. Files in /tmp now live in memory, so large temporary files count against RAM. New installs use chrony instead of systemd-timesyncd, and OpenSSH 10.2 removed DSA.
The cheapest test: build your image or service on ubuntu:26.04, run your test suite, and read the 24.04 and 26.04 release notes for the packages you depend on.
Sources
- Canonical: release cycle, Expanded Security Maintenance, 22.04 release notes, the 20.04 ESM announcement, Ubuntu Pro pricing and the Ubuntu Pro store: support dates, coverage and prices
- distro-info-data and endoflife.date: Ubuntu: day-precision dates, and the dates in the status box, MIT licensed
- Upgrading: Ubuntu Server upgrade guide, 24.04 release notes, 26.04 LTS summary, 26.04 changes since 25.10, 24.04 to 26.04.1 upgrades enabled, Pro Client attach and security-status, and postgresql-common
- Packages: Ubuntu archive versions, Python in Ubuntu releases, python3.10 publishing history and changelog, and the 24.04 Python file list
- Python: PEP 619, PEP 668, pip's error, and What's New in 3.12 and 3.13
- CI and platforms: runner-images #14254, #14747 and #14748, Azure Pipelines deprecation schedule, Heroku stacks, Heroku-22 and end-of-life FAQ, and CircleCI's Linux VM support policy
- Cloud: AKS node images and OS versions, GKE release notes, Canonical's EKS AMIs, AWS Deep Learning AMI support policy, Systems Manager instance information and Azure image names
- Images and repositories: Docker official images and the 20.04 removal, Docker Engine 28 release notes, PostgreSQL apt, deadsnakes, .NET on Ubuntu, CUDA installation guide and REP 2000
- Scanners: Tenable plugins 201473 and 201388, and Tenable's SEoL announcement
- Kubernetes cgroup documentation: the cgroup check and Ubuntu's cgroup v2 default
Common questions
When is Ubuntu 22.04 end of life?
Is Ubuntu 22.04 still supported?
ubuntu-22.04 images on 17 April 2027, and Heroku's heroku-22 stack reaches end of life on 30 April 2027.What happens when Ubuntu 22.04 reaches end of life?
apt keeps working. Canonical stops publishing free security fixes, so a machine without Ubuntu Pro collects unpatched CVEs. Vendor repositories leave too: for 20.04, Docker dropped its packages the day before standard support ended, and PostgreSQL's apt repository two months later. Tenable's scanner plugin for 22.04 reports it as unsupported from 1 June 2027.Can I upgrade Ubuntu 22.04 directly to 26.04?
do-release-upgrade takes 22.04 to 24.04, and a second run takes 24.04 to 26.04. Upgrades from 24.04 to 26.04.1 have been offered since 29 September 2026. A fresh install, a rebuilt container image or a new CI runner can go straight to 26.04.Should I upgrade to Ubuntu 24.04 or 26.04?
Is Ubuntu Pro free, and what does it cost?
When does GitHub Actions remove the ubuntu-22.04 runner?
ubuntu-22.04 or ubuntu-22.04-arm are terminated with an error. ubuntu-latest moves to 26.04 by 19 November 2026.Is Python 3.10 still patched on Ubuntu 22.04?
python3.10 package is in Main and Canonical still backports fixes into it: version 3.10.12-1~22.04.18, published on 8 September 2026, fixed two CVEs. That continues until May 2027, and with Ubuntu Pro until May 2032.Also on the calendar
End-of-life dates for the rest of your stack.
- Kubernetes end of life3 supportedNext to end: 1.35, 28 Feb 2027
- Microsoft .NET end of life2 supportedNext to end: 11, 14 Nov 2028
- Node.js end of life3 supportedNext to end: 22, 30 Apr 2027
- OpenSSL end of life3 supportedNext to end: 4.0, 14 May 2027
- PHP end of life5 supportedNext to end: 8.2, 31 Dec 2026
- PostgreSQL end of life5 supportedNext to end: 15, 11 Nov 2027
- Python end of life5 supportedNext to end: 3.11, Oct 2027
- Ubuntu end of life4 supportedNext to end: 22.04, 1 Jun 2027
Dates checked against endoflife.date (MIT), and the end-of-life date against Ubuntu (distro-info-data). How we check datesReport a wrong dateEvery Ubuntu version