Rocky Linux 10 · Version Status
Rocky Linux 10 End of Life Date
Rocky Linux 10 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Rocky Linux 10 is actively supported. EOL date: May 31, 2035.
EOL Date
May 31, 2035
3309 days remaining
Latest Release
10.1
Standard release
Release Date
Jun 11, 2025
Rocky Linux 10 series
| Version | Latest | EOL Date | Status |
|---|
| 8 |
8.10 |
May 31, 2029 |
Active |
| 9 |
9.7 |
May 31, 2032 |
Active |
| → 10 |
10.1 |
May 31, 2035 |
Active |
What does Rocky Linux 10 end of life mean?
When Rocky Linux 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 Rocky Linux 10 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Rocky Linux 10 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Rocky Linux 10 reach end of life?
Rocky Linux 10 reached end of life on May 31, 2035. That is 3309 days remaining.
Is Rocky Linux 10 still supported?
Yes, Rocky Linux 10 is currently supported. The EOL date is May 31, 2035.
What should I upgrade to from Rocky Linux 10?
The recommended upgrade from Rocky Linux 10 is
Rocky Linux 10 — the latest actively supported version. Check the
Rocky Linux full timeline for all supported versions.
What are the security risks of running Rocky Linux 10 past EOL?
When Rocky Linux 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 Rocky Linux should migrate immediately or implement compensating controls.