Ubuntu end of life dates, plus Debian, RHEL, AlmaLinux, Rocky and CentOS
As of November 15, 2026, Ubuntu 22.04, 24.04 and 26.04 LTS still get free security updates, while 18.04 and 20.04 get them only through Ubuntu Pro. RHEL 8, AlmaLinux 8 and Rocky Linux 8 are supported until May 31, 2029. Debian 12 is in LTS until June 30, 2028, and CentOS Linux 7 reached end of life on June 30, 2024.
Run cat /etc/os-release to see what a server runs. A release past its end of life gets no new security fixes, so update tools report nothing to install while new vulnerabilities stay open.
Ubuntu end of life dates (LTS releases)
Canonical publishes month-level dates. Each LTS release gets 5 years of standard security maintenance for packages in the Main repository. Ubuntu Pro adds Expanded Security Maintenance (ESM), which covers Main and Universe for 10 years in total. The Legacy add-on adds 5 more, for 15.
| Release | Standard support ends | ESM ends (Ubuntu Pro) | Legacy add-on ends | Status on Nov 15, 2026 |
|---|---|---|---|---|
| 18.04 LTS (Bionic Beaver) | May 2023 | May 2028 | May 2033 | Past standard support: security fixes only with Ubuntu Pro |
| 20.04 LTS (Focal Fossa) | May 2025 | May 2030 | May 2035 | Past standard support: security fixes only with Ubuntu Pro |
| 22.04 LTS (Jammy Jellyfish) | May 2027 | May 2032 | May 2037 | Supported, about six months of standard support left |
| 24.04 LTS (Noble Numbat) | May 2029 | May 2034 | May 2039 | Supported |
| 26.04 LTS (Resolute Raccoon) | May 2031 | May 2036 | May 2041 | Supported (newest LTS) |
Source: ubuntu.com release cycle. Interim releases get only 9 months (26.10 until July 2027), which is why most servers run LTS releases. Ubuntu Pro is free for personal use on up to 5 physical machines.
Where sources disagree: endoflife.date lists exact days and puts the ESM ends in April (for example April 26, 2028 for 18.04). Canonical's page says May for every ESM end, so we use May.
Debian end of life dates (security support, LTS and ELTS)
Debian has three layers. The Debian security team supports a release for about three years. Debian LTS, run by volunteers and companies, extends it to five years for a list of architectures; how many packages it properly supports depends on the funding it gets. Extended LTS (ELTS) is a paid offering from Freexian that can reach ten years, and it's not an official Debian project.
| Release | Released | Security team support ends | LTS ends | ELTS ends (paid) | Status on Nov 15, 2026 |
|---|---|---|---|---|---|
| 10 (buster) | July 6, 2019 | Sept 10, 2022 | June 30, 2024 | June 30, 2029 | Past end of life; paid ELTS only |
| 11 (bullseye) | Aug 14, 2021 | Aug 14, 2024 | Aug 31, 2026 | June 30, 2031 | Past end of life since Aug 31, 2026; paid ELTS only |
| 12 (bookworm) | June 10, 2023 | July 11, 2026 | June 30, 2028 | June 30, 2033 | Supported by Debian LTS (now “oldstable”) |
| 13 (trixie) | Aug 9, 2025 | Aug 9, 2028 | June 30, 2030 | June 30, 2035 | Fully supported (current stable) |
Sources: debian.org releases, the LTS schedule and the ELTS page. Debian 12 LTS covers i386, amd64, armhf, arm64 and ppc64el.
Where sources disagree: for the end of Debian 12's regular security support, debian.org says July 11, 2026, the DebianReleases wiki page says 2026-07-12, and the LTS wiki lists LTS from 2026-06-11. We use debian.org. When we checked, Debian's pages still labeled bullseye as being in LTS, but they also give its LTS end as August 31, 2026, which has passed.
RHEL end of life dates (RHEL 7, 8, 9 and 10)
Red Hat gives each major release a 10-year life cycle in two phases. Full Support brings errata, new minor releases and hardware enablement. Maintenance Support brings security and selected bug-fix errata only. After that comes the Extended Life Phase, where Red Hat ships no bug fixes or security fixes unless you buy an extended-support add-on.
| Release | Full Support ends | Maintenance Support ends | Paid extended support ends | Status on Nov 15, 2026 |
|---|---|---|---|---|
| RHEL 7 | Aug 6, 2019 | June 30, 2024 | May 31, 2029 (ELS, 7.9 only) | Past maintenance; fixes only with the paid ELS add-on |
| RHEL 8 | May 31, 2024 | May 31, 2029 | May 31, 2033 (8.10) | Supported (Maintenance Support) |
| RHEL 9 | May 31, 2027 | May 31, 2032 | May 31, 2036 (9.10) | Supported (Full Support) |
| RHEL 10 | May 31, 2030 | May 31, 2035 | May 31, 2039 (10.10) | Supported (Full Support) |
Sources: Red Hat's life cycle policy and life cycle data for RHEL 8 to 10, and Red Hat's RHEL 7 end-of-maintenance page. Red Hat's policy says Extended Life Cycle Premium (ELCP) replaces the old ELS add-on from RHEL 8.10 on June 1, 2029, with four extra years for each release's last minor version.
Where sources disagree: older articles give June 30, 2028 for RHEL 7 ELS and May 31, 2032 for RHEL 8 extended support. Red Hat's current pages say May 31, 2029 and May 31, 2033, and we use those. The RHEL 7 Full Support date comes from endoflife.date, because Red Hat's current page no longer lists it.
Minor releases matter too. Under a standard subscription each minor release is maintained for about six months, so a RHEL 9 server held on an old minor version stops getting fixes unless its subscription covers longer minor-release support. And some Application Streams (language runtimes, databases) have shorter life cycles than the 10-year major release.
AlmaLinux and Rocky Linux end of life dates
AlmaLinux and Rocky Linux follow RHEL's major-release dates. Both projects publish the same dates: “active” or “general” support (fixes and updates) until the end of RHEL's Full Support, then security-only support until the end of Maintenance Support.
| Release | Active / general support ends | Security support ends | Status on Nov 15, 2026 |
|---|---|---|---|
| AlmaLinux 8, Rocky Linux 8 | May 31, 2024 | May 31, 2029 | Supported, security fixes only (latest minor: 8.10) |
| AlmaLinux 9, Rocky Linux 9 | May 31, 2027 | May 31, 2032 | Supported (latest minor: 9.8) |
| AlmaLinux 10, Rocky Linux 10 | May 31, 2030 | May 31, 2035 | Supported (latest minor: 10.2) |
Sources: AlmaLinux release notes and Rocky Linux releases; endoflife.date agrees on every date. Rocky Linux states that no minor release is supported once the next one ships, so a server held on an old minor release is unpatched even though its major version is supported. Our AlmaLinux 9.6 test VM showed this before its first update: 248 security advisories were pending (2 Critical, 129 Important), and the fixed packages in the list came from the newer 9.7 and 9.8 releases.
CentOS end of life dates
| Release | End of life | Status on Nov 15, 2026 |
|---|---|---|
| CentOS Linux 7 | June 30, 2024 | Past end of life |
| CentOS Linux 8 | Dec 31, 2021 | Past end of life |
| CentOS Stream 8 | May 31, 2024 | Past end of life |
| CentOS Stream 9 | May 31, 2027 (end of RHEL 9 Full Support) | Supported |
| CentOS Stream 10 | May 31, 2030 (end of RHEL 10 Full Support) | Supported |
Sources: the CentOS blog, the CentOS Linux 8 EOL page and the CentOS download page. After each end date, the packages moved to vault.centos.org and no more updates were published. CentOS Stream is not a drop-in replacement for the old CentOS Linux: each Stream version ends when RHEL's Full Support ends, five years before RHEL's own Maintenance Support does.
What does end of life mean for patching?
An end-of-life server keeps running; what stops is the flow of fixes. Every vulnerability found after the date stays open, and nothing on the server tells you:
- Update tools report a clean system.
apt upgradeanddnf upgradefind nothing, because there's nothing new to find. unattended-upgrades logsNo packages found that can be upgraded unattendedevery day, exactly as it does on a fully patched server. - Many scanners look clean too. A scanner that compares installed packages with the distribution's list of fixed versions can only report fixes that exist. When the vendor stops releasing fixes, “nothing to fix” can mean “no fixes will ever come”, not “no vulnerabilities”.
- Partial coverage looks like full coverage. On Ubuntu, Canonical's standard security maintenance covers Main; Universe packages get Canonical's fixes through Ubuntu Pro. Debian LTS skips some packages and architectures. RHEL's shorter-lived Application Streams can end before the release does.
Ubuntu's Pro client says it plainly: on an LTS release past standard support without ESM, pro security-status reports the machine as “NOT receiving security patches because the LTS period has ended” (Ubuntu Pro Client documentation). Our guide to checking for security updates and unattended-upgrades guide cover how to confirm patches are really arriving.
How do I check which version a server runs?
/etc/os-release exists on every systemd-based distribution. Here it is on the three systems we tested:
$ cat /etc/os-release # Ubuntu server
PRETTY_NAME="Ubuntu 24.04.5 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.5 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
... (trimmed)
$ cat /etc/os-release # Debian test VM
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
... (trimmed)
$ cat /etc/debian_version
12.15
$ grep -E '^(PRETTY_NAME|VERSION_ID|SUPPORT_END)=' /etc/os-release # AlmaLinux test VM, after its upgrade to 9.8
VERSION_ID="9.8"
PRETTY_NAME="AlmaLinux 9.8 (Olive Jaguar)"
SUPPORT_END=2032-06-01
$ cat /etc/redhat-release
AlmaLinux release 9.8 (Olive Jaguar)
VERSION_IDgives the major version to look up above. On AlmaLinux it includes the minor release (9.8), which matters on the RHEL family.SUPPORT_END, where present, is the first day without support, per the os-release specification. AlmaLinux 9 sets2032-06-01, matching its May 31, 2032 end. Our Ubuntu 24.04 and Debian 12 systems don't set it, so don't rely on it across a fleet.
hostnamectl adds the kernel. On Ubuntu, pro status shows whether the machine is attached to Ubuntu Pro:
$ hostnamectl
Static hostname: web-01
... (trimmed)
Operating System: Ubuntu 24.04.5 LTS
Kernel: Linux 6.8.0-149-generic
Architecture: x86-64
... (trimmed)
$ pro status
... (trimmed)
SERVICE AVAILABLE DESCRIPTION
... (trimmed)
esm-apps yes Expanded Security Maintenance for Applications
esm-infra yes Expanded Security Maintenance for Infrastructure
... (trimmed)
livepatch yes Canonical Livepatch service
... (trimmed)
This machine is not attached to an Ubuntu Pro subscription.
See https://ubuntu.com/pro
On 24.04 that's fine until May 2029. On 18.04 or 20.04, “not attached” means no security fixes at all. For a fleet, loop over the servers with SSH and print PRETTY_NAME from each one's /etc/os-release.
What are your options when a version reaches end of life?
| Option | How | Watch out for |
|---|---|---|
| Upgrade in place | Ubuntu: do-release-upgrade, one LTS at a time (20.04 → 22.04 → 24.04), offered after the new LTS's first point release. Debian: only from the previous release, so 11 goes to 12 before 13. RHEL: Leapp, one major version at a time. AlmaLinux and Rocky: AlmaLinux's ELevate project (CentOS 7 to EL 8, then EL 8 → 9 → 10). | Ubuntu's and Debian's upgrade guides both insist on a full backup first. Third-party repositories and locally changed config files can block or break an upgrade, so try it on a copy of the server. |
| Rebuild on a supported release | Build a new server on a current release, move data and config, switch traffic. | More planning, but you end up with a clean system and a tested rebuild. |
| Pay for extended support | Ubuntu Pro (ESM and Legacy), RHEL ELS or ELCP, Debian ELTS from Freexian. Third parties sell support for CentOS 7. | It buys time, not a plan. Coverage is often narrower: RHEL 7 ELS covers certain critical-impact fixes, and ELTS covers the packages its subscribers choose. |
| Switch distribution | Rocky's migrate2rocky converts EL 8 or 9 systems (CentOS, AlmaLinux, RHEL, Oracle Linux) to Rocky; AlmaLinux's ELevate can move between EL distributions while upgrading. | A conversion changes every package source at once. Test it on a snapshot first. |
AlmaLinux vs Rocky Linux: which should you choose?
For most servers it doesn't matter much. Both are free, both are built to run software made for RHEL, and both publish the same end-of-life dates. The real differences:
| AlmaLinux | Rocky Linux | |
|---|---|---|
| Support dates | 8: May 2029 · 9: May 2032 · 10: May 2035 | Same |
| Compatibility goal | Binary (application) compatibility with RHEL since July 2023, no longer bug-for-bug | Describes itself as 100% bug-for-bug compatible with RHEL, rebuilt from RHEL sources |
| Version 10 on older x86 CPUs | Ships an extra x86-64-v2 build for older hardware | Requires x86-64-v3, like RHEL 10 |
| Changes from RHEL (version 10) | Some, for example frame pointers on by default and drivers re-enabled for hardware RHEL dropped | None intended (its goal is bug-for-bug) |
| Run by | AlmaLinux OS Foundation, a 501(c)(6) with a community-elected board | Hosted by the Rocky Enterprise Software Foundation (RESF) |
| Migration tooling | ELevate (major-version upgrades) | migrate2rocky (convert EL 8 and 9 to Rocky) |
Sources: the AlmaLinux OS Foundation page, the AlmaLinux compatibility announcement, Rocky Linux's home page and about page, and each project's version 10 release notes.
Pick Rocky Linux for behavior as close to RHEL as possible. Pick AlmaLinux if you need version 10 on CPUs older than x86-64-v3, or its re-enabled drivers. Either way, check which one your software vendors support, and keep it on the latest minor release.
How we checked this: Every date was checked on 14 Nov 2026 (UTC) against the vendor's own lifecycle page and cross-checked with endoflife.date; where they differ, we use the vendor's date and say so. The version commands were run on 14 Nov 2026 (UTC) on an Ubuntu 24.04.5 LTS server, a Debian 12.15 test VM and an AlmaLinux test VM: its pending advisories at 9.6, before its first update, and its os-release output after its upgrade to 9.8. Hostnames are changed. Anything we didn't run ourselves comes from the official documentation listed under Sources.
Check which CVEs are really open on your server
HostCrust Patch Proof compares every installed package with your distribution's own security data. It counts fixes your distro backported and checks the kernel that is actually running, not just the one on disk. Read-only, no root, free.
Check that auto-patching is really working
unattended-upgrades-check runs 12 read-only checks over SSH on Ubuntu, Debian, AlmaLinux and Rocky Linux servers (unattended-upgrades or dnf-automatic) and gives each server a PASS, WARN or FAIL. Free and open source (Apache-2.0).
FAQ
When does Ubuntu 22.04 reach end of life?
Standard security maintenance for Ubuntu 22.04 LTS ends in May 2027. After that, security fixes continue only with Ubuntu Pro (ESM) until May 2032, or May 2037 with the Legacy add-on. Plan the upgrade before then.
Is RHEL 8 end of life?
No. RHEL 8 left Full Support on May 31, 2024 and is in Maintenance Support until May 31, 2029, which still delivers security errata. Red Hat's paid extended support for RHEL 8.10 then runs to May 31, 2033.
Is CentOS 7 still safe to use?
No. CentOS Linux 7 reached end of life on June 30, 2024. No updates have been published since, so every vulnerability found after that date stays open. Move to AlmaLinux, Rocky Linux or RHEL, or buy third-party extended support while you migrate.
When does Debian 12 reach end of life?
Debian 12's regular security support ended on July 11, 2026, and Debian LTS now covers it until June 30, 2028. LTS covers some architectures and not every package. After that, only the paid ELTS offering continues it, to June 30, 2033.
Is RHEL 7 out of support?
For most users, yes. RHEL 7's Maintenance Support ended on June 30, 2024, so a standard subscription no longer gets its security advisories. Red Hat's paid Extended Life Cycle Support (ELS) add-on continues certain critical-impact security fixes and selected urgent bug fixes for RHEL 7.9 until May 31, 2029.
How long will Rocky Linux 8 and AlmaLinux 8 be supported?
Both get security updates until May 31, 2029, matching RHEL 8's Maintenance Support. Their active (general) support ended on May 31, 2024. Keep them on the latest minor release, 8.10.
Is Ubuntu 20.04 still supported?
Only through Ubuntu Pro. Standard security maintenance ended in May 2025. With Ubuntu Pro attached, ESM provides security updates until May 2030, or May 2035 with the Legacy add-on. Without Pro, a 20.04 server gets no new security fixes.
Sources
- Ubuntu release cycle (Canonical): standard support, ESM and Legacy add-on dates
- Ubuntu Pro: free for personal use on up to 5 physical machines
- Ubuntu Pro Client: what security-status reports
- Ubuntu Server documentation: upgrade your release
- Debian releases index (release, EOL, LTS and ELTS dates)
- Debian 12 bookworm release page
- Debian Wiki: LTS schedule
- Debian Wiki: Extended LTS (Freexian, not an official Debian project)
- Debian 13 release notes: upgrading from Debian 12
- Red Hat Enterprise Linux life cycle and errata policy
- Red Hat product life cycle data for RHEL 8, 9 and 10
- Red Hat: RHEL 7 end of maintenance and ELS to May 31, 2029
- Red Hat: upgrading RHEL in place with Leapp
- AlmaLinux release notes and life cycle
- AlmaLinux 10.0 release notes (x86-64-v2 build and other changes)
- AlmaLinux blog: the decision to aim for binary compatibility (July 13, 2023)
- AlmaLinux ELevate: in-place upgrades between major versions
- AlmaLinux OS Foundation: a registered 501(c)(6) with a community-elected board
- Rocky Linux: designed to be 100% bug-for-bug compatible with RHEL
- Rocky Linux: about the project (hosted by the Rocky Enterprise Software Foundation)
- Rocky Linux releases and support dates
- Rocky Linux 10.0 release notes (x86-64-v3 baseline)
- CentOS blog: end dates for CentOS Stream 8 and CentOS Linux 7
- CentOS: CentOS Linux 8 end of life
- CentOS download page: CentOS Stream 9 and 10 end dates
- os-release(5): SUPPORT_END and other fields
- endoflife.date (cross-check for every date above)