RHEL 8 · Version Status
RHEL 8 End of Life Date
RHEL 8 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
RHEL 8 is actively supported. EOL date: May 31, 2029.
EOL Date
May 31, 2029
1118 days remaining
Latest Release
8.10
LTS release
Release Date
May 7, 2019
RHEL 8 series
| Version | Latest | EOL Date | Status |
|---|
| 4 |
4.9 |
Feb 29, 2012 |
EOL |
| 5 LTS |
5.11 |
Mar 31, 2017 |
EOL |
| 6 LTS |
6.10 |
Nov 30, 2020 |
EOL |
| 7 LTS |
7.9 |
Jun 30, 2024 |
EOL |
| → 8 LTS |
8.10 |
May 31, 2029 |
Active |
| 9 LTS |
9.7 |
May 31, 2032 |
Active |
| 10 LTS |
10.1 |
May 31, 2035 |
Active |
What does RHEL 8 end of life mean?
When RHEL 8 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running RHEL 8 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to RHEL 10 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does RHEL 8 reach end of life?
RHEL 8 reached end of life on May 31, 2029. That is 1118 days remaining.
Is RHEL 8 still supported?
Yes, RHEL 8 is currently supported. The EOL date is May 31, 2029.
What should I upgrade to from RHEL 8?
The recommended upgrade from RHEL 8 is
RHEL 10 — the latest actively supported version. Check the
RHEL full timeline for all supported versions.
What are the security risks of running RHEL 8 past EOL?
When RHEL 8 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL RHEL should migrate immediately or implement compensating controls.