Red Hat OpenShift End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Red Hat OpenShift versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 4.1 | 4.1.41 | Jun 18, 2019 | May 5, 2020 | 2240 days past EOL | EOL |
| 4.2 | 4.2.36 | Oct 29, 2019 | Jul 13, 2020 | 2171 days past EOL | EOL |
| 4.3 | 4.3.40 | Feb 12, 2020 | Oct 27, 2020 | 2065 days past EOL | EOL |
| 4.4 | 4.4.33 | May 18, 2020 | Feb 24, 2021 | 1945 days past EOL | EOL |
| 4.5 | 4.5.41 | Jul 16, 2020 | Jul 27, 2021 | 1792 days past EOL | EOL |
| 4.6 | 4.6.62 | Nov 9, 2020 | Oct 27, 2022 | 1335 days past EOL | EOL |
| 4.7 | 4.7.60 | Feb 24, 2021 | Aug 24, 2022 | 1399 days past EOL | EOL |
| 4.8 | 4.8.57 | Jul 27, 2021 | Jan 27, 2023 | 1243 days past EOL | EOL |
| 4.9 | 4.9.59 | Oct 18, 2021 | Apr 18, 2023 | 1162 days past EOL | EOL |
| 4.10 | 4.10.67 | Mar 10, 2022 | Sep 10, 2023 | 1017 days past EOL | EOL |
| 4.11 | 4.11.59 | Aug 10, 2022 | Feb 10, 2024 | 864 days past EOL | EOL |
| 4.12 | 4.12.82 | Jan 17, 2023 | Jul 17, 2024 | 706 days past EOL | EOL |
| 4.13 | 4.13.61 | May 17, 2023 | Nov 17, 2024 | 583 days past EOL | EOL |
| 4.14 | 4.14.58 | Oct 31, 2023 | May 1, 2025 | 418 days past EOL | EOL |
| 4.15 | 4.15.59 | Feb 27, 2024 | Aug 27, 2025 | 300 days past EOL | EOL |
| 4.16 | 4.16.52 | Jun 27, 2024 | Dec 27, 2025 | 178 days past EOL | EOL |
| 4.17 | 4.17.43 | Oct 1, 2024 | Apr 1, 2026 | 83 days past EOL | EOL |
| 4.18 | 4.18.28 | Feb 25, 2025 | Aug 25, 2026 | 63 days remaining | Warning |
| 4.19 | 4.19.18 | Jun 17, 2025 | Dec 17, 2026 | 177 days remaining | Warning |
| 4.20 | 4.20.4 | Oct 21, 2025 | Apr 21, 2027 | 302 days remaining | Active |
What does Red Hat OpenShift end of life mean for your organization?
When a version of Red Hat OpenShift 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 Red Hat OpenShift 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Red Hat OpenShift versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →