RHEL · Lifecycle Status

RHEL End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all RHEL versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

RHEL 8.10 is actively supported. Next EOL: version 8 on May 31, 2029.
Latest Active
8.10
8 series
Next EOL
8
May 31, 2029
Active Versions
3
of 7 total
EOL Versions
4
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 200520062007200820092010201120122013201420152016201720182019202020212022202320242025202620272028202920302031203220332034203545678910TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
4 4.9 Feb 15, 2005 Feb 29, 2012 5183 days past EOL EOL
5 LTS 5.11 Mar 15, 2007 Mar 31, 2017 3326 days past EOL EOL
6 LTS 6.10 Nov 10, 2010 Nov 30, 2020 1986 days past EOL EOL
7 LTS 7.9 Jun 10, 2014 Jun 30, 2024 678 days past EOL EOL
8 LTS 8.10 May 7, 2019 May 31, 2029 1118 days remaining Active
9 LTS 9.7 May 18, 2022 May 31, 2032 2214 days remaining Active
10 LTS 10.1 May 20, 2025 May 31, 2035 3309 days remaining Active

What does RHEL end of life mean for your organization?

When a RHEL version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL RHEL should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL RHEL versions. This is a bridge, not a permanent solution — plan your migration in parallel.

TuxCare
Extended RHEL Support

Extended security support for RHEL beyond Red Hat EOL dates.

Learn More →
endoflife.ai
Check Your Full Stack

Upload your dependency file and scan your entire stack for EOL risk in seconds. Free, no account required.

Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for RHEL?
The next RHEL version reaching EOL is 8 on May 31, 2029. See the full table above for all version EOL dates.
What is the latest supported version of RHEL?
The latest active version of RHEL is 8.10. Always verify against the table above as support windows can change.
What happens when RHEL reaches end of life?
When RHEL reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of RHEL?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL RHEL versions?
Yes — TuxCare offers extended support for EOL RHEL versions, providing continued security patches while you plan your migration.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →