Red Hat Satellite End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Red Hat Satellite versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Red Hat Satellite 6.19 is supported until November 1, 2027, its end-of-support date. Active support for Red Hat Satellite 6.19 ends on November 1, 2026; security fixes continue until that end-of-life date. The next Red Hat Satellite version to reach end of life is 6.17, on November 28, 2026. 17 of 20 tracked Red Hat Satellite versions are past end of life; the most recent to reach it, 6.16, did so on May 31, 2026. The full Red Hat Satellite lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 6.0 | 6.0.8 | Sep 10, 2014 | Feb 21, 2018 | — | 3136 days past EOL | EOL |
| 6.1 | 6.1.12 | Aug 12, 2015 | Oct 30, 2018 | — | 2885 days past EOL | EOL |
| 6.2 | 6.2.16 | Jul 27, 2016 | May 31, 2019 | — | 2672 days past EOL | EOL |
| 6.3 | 6.3.5 | Feb 21, 2018 | May 31, 2019 | — | 2672 days past EOL | EOL |
| 6.4 | 6.4.4 | Oct 16, 2018 | Apr 30, 2020 | — | 2337 days past EOL | EOL |
| 6.5 | 6.5.3 | May 14, 2019 | Oct 31, 2020 | — | 2153 days past EOL | EOL |
| 6.6 | 6.6.3 | Oct 22, 2019 | May 14, 2021 | — | 1958 days past EOL | EOL |
| 6.7 | 6.7.5 | Apr 14, 2020 | Nov 30, 2021 | — | 1758 days past EOL | EOL |
| 6.8 | 6.8.6 | Oct 27, 2020 | Jul 31, 2022 | — | 1515 days past EOL | EOL |
| 6.9 | 6.9.10 | Apr 21, 2021 | Nov 30, 2022 | — | 1393 days past EOL | EOL |
| 6.10 | 6.10.7.2 | Nov 16, 2021 | May 31, 2023 | — | 1211 days past EOL | EOL |
| 6.11 | 6.11.5.7 | Jul 5, 2022 | Jan 31, 2024 | — | 966 days past EOL | EOL |
| 6.12 | 6.12.5.3 | Nov 16, 2022 | May 31, 2024 | — | 845 days past EOL | EOL |
| 6.13 | 6.13.7.3 | May 3, 2023 | Nov 30, 2024 | — | 662 days past EOL | EOL |
| 6.14 | 6.14.4.5 | Nov 8, 2023 | May 30, 2025 | — | 481 days past EOL | EOL |
| 6.15 | 6.15.5.8 | Apr 23, 2024 | Nov 30, 2025 | — | 297 days past EOL | EOL |
| 6.16 | 6.16.10 | Nov 5, 2024 | May 31, 2026 | May 31, 2027 Extended support |
115 days past EOL | EOL |
| 6.17 | 6.17.11 | May 6, 2025 | Nov 28, 2026 | — | 66 days remaining | Warning |
| 6.18 | 6.18.9 | Nov 4, 2025 | May 1, 2027 | — | 220 days remaining | Active |
| 6.19 | 6.19.4 | May 6, 2026 | Nov 1, 2027 | — | 404 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/redhat-satellite)
Red Hat Satellite release and support pattern
Across the 20 release lines with a published release date, Red Hat Satellite has shipped a new line roughly every 6 months (median interval). A line typically stays in standard support for about 1.6 years from its release to its standard-support end date.
Of the 20 release lines tracked, 17 are past end of life and 3 are still within support. The newest line, 6.19, was released May 6, 2026. The next scheduled end of life is 6.17 on November 28, 2026 — 65 days from this build. The longest-supported line currently published is 6.19, to November 1, 2027. Upstream also publishes an extended-support phase for 1 line, shown in the table above.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Red Hat Satellite end of life mean for your organization?
When a version of Red Hat Satellite 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Red Hat 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.
Your options when Red Hat Satellite reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Red Hat Satellite versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Red Hat Satellite has 17 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Red Hat Satellite is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."