Redhat Satellite End of Life Dates
other
Developers rely on Redhat Satellite to manage and track the lifecycle of their Red Hat systems, ensuring seamless updates and security patches. Created to simplify the management of Red Hat deployments, Redhat Satellite has been a cornerstone for system administrators since its inception. Maintained by Red Hat, this tool has become an essential component for teams seeking to streamline their system management processes. By utilizing Redhat Satellite, developers can efficiently plan and execute upgrades, minimizing downtime and maximizing system security.
The end-of-life landscape for Redhat Satellite is complex, with a total of 20 versions released to date. Of these, 17 versions have reached their end-of-life, leaving only 3 active versions currently supported. The latest stable version, 6.19.1, is the most recent release, offering the latest features and security patches. However, version 6.17 is next in line to reach its end-of-life, with support set to expire on November 30, 2026. This follows the recent end-of-life of version 6.16, which occurred on May 31, 2026. Staying on top of these end-of-life dates is crucial for developers to ensure their systems remain secure and supported.
With no tracked Common Vulnerabilities and Exposures (CVEs), Redhat Satellite presents a clean security slate, boasting zero critical CVEs. As a result, there is no most affected version, and no known vulnerabilities pose an immediate threat to system security. Nevertheless, developers should remain vigilant and proactive in planning their upgrades, taking advantage of the latest security patches and features offered by the active versions of Redhat Satellite. By doing so, they can ensure the continued security and integrity of their systems, even in the absence of known vulnerabilities.
Last updated: Oct 23, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 6.19 | May 6, 2026 | Nov 1, 2026 | Nov 1, 2027 | in 374d | 6.19.5 | — | Active | |
| 6.18 | Nov 4, 2025 | May 6, 2026 | May 1, 2027 | in 190d | 6.18.10 | — | Active | |
| 6.17 | May 6, 2025 | Nov 30, 2025 | Nov 30, 2026 | in 38d | 6.17.12 | — | EOL soon | |
| 6.16 | Nov 5, 2024 | May 31, 2025 | May 31, 2026 | 145d ago | 6.16.10 | — | EOL | |
| 6.15 | Apr 23, 2024 | Nov 30, 2024 | Nov 30, 2025 | 327d ago | 6.15.5.8 | — | EOL | |
| 6.14 | Nov 8, 2023 | May 31, 2024 | May 31, 2025 | 510d ago | 6.14.4.5 | — | EOL | |
| 6.13 | May 3, 2023 | Nov 30, 2023 | Nov 30, 2024 | 692d ago | 6.13.7.3 | — | EOL | |
| 6.12 | Nov 16, 2022 | May 31, 2023 | May 31, 2024 | 875d ago | 6.12.5.3 | — | EOL | |
| 6.11 | Jul 5, 2022 | Nov 30, 2022 | Jan 31, 2024 | 996d ago | 6.11.5.7 | — | EOL | |
| 6.10 | Nov 16, 2021 | Jun 30, 2022 | May 31, 2023 | 1241d ago | 6.10.7.2 | — | EOL | |
| 6.9 | Apr 21, 2021 | Nov 30, 2021 | Nov 30, 2022 | 1423d ago | 6.9.10 | — | EOL | |
| 6.8 | Oct 27, 2020 | Apr 30, 2021 | Jul 31, 2022 | 1545d ago | 6.8.6 | — | EOL | |
| 6.7 | Apr 14, 2020 | Oct 31, 2020 | Nov 30, 2021 | 1788d ago | 6.7.5 | — | EOL | |
| 6.6 | Oct 22, 2019 | Apr 30, 2020 | May 14, 2021 | 1988d ago | 6.6.3 | — | EOL | |
| 6.5 | May 14, 2019 | Oct 31, 2019 | Oct 31, 2020 | 2183d ago | 6.5.3 | — | EOL | |
| 6.4 | Oct 16, 2018 | May 31, 2019 | Apr 30, 2020 | 2367d ago | 6.4.4 | — | EOL | |
| 6.3 | Feb 21, 2018 | Oct 30, 2018 | May 31, 2019 | 2702d ago | 6.3.5 | — | EOL | |
| 6.2 | Jul 27, 2016 | Feb 21, 2018 | May 31, 2019 | 2702d ago | 6.2.16 | — | EOL | |
| 6.1 | Aug 12, 2015 | Jul 27, 2016 | Oct 30, 2018 | 2915d ago | 6.1.12 | — | EOL | |
| 6.0 | Sep 10, 2014 | Aug 12, 2015 | Feb 21, 2018 | 3166d ago | 6.0.8 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
