RHEL 10 · Version Status

RHEL 10 End of Life Date

RHEL 10 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

✓ RHEL 10 is actively supported. EOL date: May 31, 2035.
📅 Get reminded before RHEL 10 reaches EOL on May 31, 2035 — alerts 90, 30 & 7 days out.
Google →
EOL Date
May 31, 2035
3217 days remaining
Latest Release
10.2
LTS release
Release Date
May 20, 2025
RHEL 10 series
Extended Support
May 31, 2039
Extended Life Cycle Support (ELS) · paid
Lifecycle detail

RHEL 10 was released on May 20, 2025 and support is scheduled to end on May 31, 2035 — a planned supported lifespan of 10 years, in line with the 10 years and 1 month median for RHEL LTS releases. It is a long-term support (LTS) release, so it carries a longer patch window than the interim releases around it. Its most recent patch is 10.2, published May 20, 2026.

← RHEL 9 All RHEL versions
50 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
30/30 Critical tier
CISA KEV Exposure
20/20 Named in 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 →  ·  View score card →
All RHEL Versions
VersionLatestEOL DateStatus
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.8 May 31, 2032 Active
→ 10 LTS 10.2 May 31, 2035 Active

What does RHEL 10 end of life mean?

When RHEL 10 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 10 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 10 reach end of life?
RHEL 10 reached end of life on May 31, 2035. That is 3217 days remaining.
Is RHEL 10 still supported?
Yes, RHEL 10 is currently supported. The EOL date is May 31, 2035.
What should I upgrade to from RHEL 10?
The recommended upgrade from RHEL 10 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 10 past EOL?
When RHEL 10 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.
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
RHEL End of Life & Support Options: When Red Hat Patches Stop
→
Data from endoflife.date API · Generated at build time · How we source data →
Related Products
UbuntuDebianCentOSSLES