Complete end-of-life dates, support windows, and security status for all Redhat Satellite versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 6.0 | 6.0.8 | Sep 10, 2014 | Feb 21, 2018 | 2999 days past EOL | EOL |
| 6.1 | 6.1.12 | Aug 12, 2015 | Oct 30, 2018 | 2748 days past EOL | EOL |
| 6.2 | 6.2.16 | Jul 27, 2016 | May 31, 2019 | 2535 days past EOL | EOL |
| 6.3 | 6.3.5 | Feb 21, 2018 | May 31, 2019 | 2535 days past EOL | EOL |
| 6.4 | 6.4.4 | Oct 16, 2018 | Apr 30, 2020 | 2200 days past EOL | EOL |
| 6.5 | 6.5.3 | May 14, 2019 | Oct 31, 2020 | 2016 days past EOL | EOL |
| 6.6 | 6.6.3 | Oct 22, 2019 | May 14, 2021 | 1821 days past EOL | EOL |
| 6.7 | 6.7.5 | Apr 14, 2020 | Nov 30, 2021 | 1621 days past EOL | EOL |
| 6.8 | 6.8.6 | Oct 27, 2020 | Jul 31, 2022 | 1378 days past EOL | EOL |
| 6.9 | 6.9.10 | Apr 21, 2021 | Nov 30, 2022 | 1256 days past EOL | EOL |
| 6.10 | 6.10.7.2 | Nov 16, 2021 | May 31, 2023 | 1074 days past EOL | EOL |
| 6.11 | 6.11.5.7 | Jul 5, 2022 | Jan 31, 2024 | 829 days past EOL | EOL |
| 6.12 | 6.12.5.3 | Nov 16, 2022 | May 31, 2024 | 708 days past EOL | EOL |
| 6.13 | 6.13.7.3 | May 3, 2023 | Nov 30, 2024 | 525 days past EOL | EOL |
| 6.14 | 6.14.4.5 | Nov 8, 2023 | May 31, 2025 | 343 days past EOL | EOL |
| 6.15 | 6.15.5.8 | Apr 23, 2024 | Nov 30, 2025 | 160 days past EOL | EOL |
| 6.16 | 6.16.8 | Nov 5, 2024 | May 31, 2026 | 22 days remaining | Warning |
| 6.17 | 6.17.8 | May 6, 2025 | Nov 30, 2026 | 205 days remaining | Active |
| 6.18 | 6.18.5 | Nov 4, 2025 | Already EOL | Supported | Active |
When a Redhat Satellite 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 Redhat Satellite 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →