RHEL 7 end of life: dates and what to upgrade to
RHEL 7 end of life dates, what each support phase means, what to upgrade to, and how to check a server by hand and with Stackurity.
TL;DR
- RHEL 7 maintenance support ended on June 30, 2024, so the release no longer gets regular security updates.
- Full support ended earlier, on August 6, 2019, and the last minor release in the line is 7.9.
- The only route to further fixes is Red Hat's Extended Life Cycle Support add-on, which runs to May 31, 2029. It is a bridge, not a destination.
- The longest supported upgrade target is RHEL 10, with maintenance support to May 31, 2035, followed by RHEL 9 to May 31, 2032 and RHEL 8 to May 31, 2029.
- Stackurity matches end-of-life dates against your inventory every day, so servers still on RHEL 7 show up in one list.
What reaches end of life and when
Red Hat Enterprise Linux 7 was released on June 10, 2014. Red Hat defines several support phases, and both Red Hat's lifecycle page for older releases and endoflife.date list the same dates for RHEL 7.
- Full support ended on August 6, 2019. In this phase Red Hat shipped new features and hardware enablement along with fixes.
- Maintenance support ended on June 30, 2024. In this phase the focus was on important security fixes and urgent bug fixes, and this is the date most people mean when they search for RHEL 7 end of life.
- Extended Life Cycle Support (ELS) add-on runs to May 31, 2029. It is an add-on from Red Hat for customers who need fixes after maintenance support ended, and Red Hat's table shows the extended life phase as ongoing.
In practice, that means a RHEL 7 server without the add-on is already past its end of life. With the add-on, the server is covered until May 31, 2029, and that is the latest date by which every RHEL 7 server should be gone.
What end of life means
When a release leaves maintenance support, it stops receiving regular security updates for newly found vulnerabilities. Every flaw discovered afterwards stays open on those servers unless you have the add-on or move on. That has three practical effects.
- Security exposure: new vulnerabilities in the kernel, libraries and services are not fixed in the base release, and attackers know that old releases are easy targets.
- Compliance and audits: auditors and customers commonly treat an unsupported operating system as a finding, which can block certifications and contracts.
- Application support: software vendors drop support for operating system releases that their own supplier no longer maintains, and a call to their support desk may end with a request to upgrade first.
Migrations from a release this old take longer than most teams expect. Applications were built and tested against an older kernel, older libraries and older language runtimes, and the gap to a current release is large. Moving in waves, starting with the least critical systems, gives you room to learn what breaks without risking the systems that matter most.
What to upgrade to
Three newer releases are listed in Red Hat's lifecycle tables. The one with the longest support comes first.
- RHEL 10: released on May 20, 2025, full support to May 31, 2030, maintenance support to May 31, 2035, and the ELS add-on to May 31, 2039.
- RHEL 9: released on May 18, 2022, full support to May 31, 2027, maintenance support to May 31, 2032, and the ELS add-on to May 31, 2036.
- RHEL 8: released on May 7, 2019, full support ended on May 31, 2024, maintenance support to May 31, 2029, and the ELS add-on to May 31, 2033.
RHEL 10 gives you the most runway, so it is the natural choice for new builds. RHEL 9 can make sense when an application is certified only for it. RHEL 8 is a poor destination, because its own maintenance support ends on the same day as the RHEL 7 add-on, May 31, 2029, so you would be facing a second migration almost at once. Follow these steps:
- List every RHEL 7 server, image and virtual machine template, with the applications each one runs and the owner of each application.
- Choose a target release for each workload, preferring RHEL 10 and using RHEL 9 only where an application requires it.
- Test the application on the target release, and read Red Hat's documentation for the upgrade paths it supports for your case. For old systems, a fresh build and a data migration is often safer than an in-place upgrade.
- Migrate in waves, keep the old server until the new one has served real traffic, and retire it afterwards.
- For anything that cannot move yet, decide whether to buy the add-on, and record the owner and the date by which that exception ends.
- Confirm that no RHEL 7 system remains in the inventory, and keep the result for your audit trail.
How to check one server by hand
Log in to the machine and run any of these commands. Each prints the release that is installed:
cat /etc/redhat-release
cat /etc/os-release
hostnamectl
rpm -q redhat-releaseIf the output names release 7, the server is covered by this guide. For a container image, run the same commands inside a container started from the image, because the base layer decides the release, not the host.
How Stackurity flags it
Stackurity keeps one live inventory of your servers, applications, repositories and container images, and matches it against end-of-life data every day. Red Hat Enterprise Linux is one of the distributions whose packages are assessed, so a RHEL 7 server shows up with its end-of-life date as well as its vulnerabilities, and each item is ranked so the most urgent upgrades come first. The remediation guide explains how the upgrade cards work, and pricing lists the plans. Runtimes installed outside a package manager are checked for end of life only. You can try it with a free trial: start a free trial.
FAQ
When does RHEL 7 reach end of life?
Maintenance support for RHEL 7 ended on June 30, 2024, according to Red Hat's lifecycle page and endoflife.date. Red Hat's Extended Life Cycle Support add-on runs to May 31, 2029.
Is RHEL 7 still getting security updates?
Not as part of regular support. Maintenance support ended on June 30, 2024, so only the Extended Life Cycle Support add-on from Red Hat provides fixes, until May 31, 2029.
What should I upgrade RHEL 7 to?
RHEL 10 has the longest support: maintenance support to May 31, 2035. RHEL 9 is supported to May 31, 2032. Pick the newest release your applications are certified for.
What is the RHEL 7 extended support end date?
The Extended Life Cycle Support add-on for RHEL 7 ends on May 31, 2029. It is an add-on from Red Hat, so check the terms with Red Hat before you rely on it.
How do I check my RHEL version?
Run cat /etc/redhat-release or cat /etc/os-release on the server. Both print the release you have installed.
Sources
Red Hat lifecycle page for older releases, Red Hat lifecycle page for current releases, endoflife.date and Stackurity product facts.