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 10.2 is actively supported. Next EOL: version 8 on May 31, 2029.
📅 Get reminded before RHEL 8 reaches EOL on May 31, 2029 — alerts 90, 30 & 7 days out.
Google →
Latest Active
10.2
10 series
Next EOL
8
May 31, 2029
Active Versions
3
of 7 total
EOL Versions
4
no longer patched
85 / 100
Critical Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
35/40
Attack Surface
30/30 Critical tier
CISA KEV Exposure
20/20 Yes — CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →
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 5228 days past EOL EOL
5 LTS 5.11 Mar 15, 2007 Mar 31, 2017 3371 days past EOL EOL
6 LTS 6.10 Nov 10, 2010 Nov 30, 2020 2031 days past EOL EOL
7 LTS 7.9 Jun 10, 2014 Jun 30, 2024 723 days past EOL EOL
8 LTS 8.10 May 7, 2019 May 31, 2029 1073 days remaining Active
9 LTS 9.8 May 18, 2022 May 31, 2032 2169 days remaining Active
10 LTS 10.2 May 20, 2025 May 31, 2035 3264 days remaining Active

What does RHEL end of life mean for your organization?

When a version of RHEL 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.

endoflife.ai
Need Extended Support?

We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.

Contact Us →
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.
When is the RHEL support end date?
The next RHEL support end date is May 31, 2029, when version 8 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of RHEL?
The latest active version of RHEL is 10.2. 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?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.
Does RHEL track end-of-life by point release (e.g. RHEL 10.1, RHEL 10.2)?
No — RHEL end-of-life dates apply to the entire 10.x release series, not individual point releases. A point release like RHEL 10.1 or RHEL 10.2 shares the same EOL date as RHEL 10. Security patches stop for the entire 10.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.
Deep Dive
Full Guide
Red Hat Enterprise Linux (RHEL) End of Life: Full Support Timeline
→

Related Products

Ubuntu
View EOL timeline →
CentOS
View EOL timeline →
Debian
View EOL timeline →
Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →