Red Hat OpenShift 4.20 · Version Status
Red Hat OpenShift 4.20 End of Life Date
Red Hat OpenShift 4.20 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
Red Hat OpenShift 4.20 is actively supported. EOL date: April 21, 2027.
📅 Get reminded before Red Hat OpenShift 4.20 reaches EOL on April 21, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Apr 21, 2027
195 days remaining
Latest Release
4.20.40
Standard release
Release Date
Oct 21, 2025
Red Hat OpenShift 4.20 series
Extended Support
Oct 21, 2027
Extended support
Lifecycle detail
Red Hat OpenShift 4.20 was released on October 21, 2025 and support is scheduled to end on April 21, 2027 — a planned supported lifespan of 1 year and 6 months, in line with the 1 year and 6 months median for Red Hat OpenShift releases. Its most recent patch is 4.20.40, published September 29, 2026.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
All Red Hat OpenShift Versions
| Version | Latest | EOL Date | Status |
|---|
| 4.1 |
4.1.41 |
May 5, 2020 |
EOL |
| 4.2 |
4.2.36 |
Jul 13, 2020 |
EOL |
| 4.3 |
4.3.40 |
Oct 27, 2020 |
EOL |
| 4.4 |
4.4.33 |
Feb 24, 2021 |
EOL |
| 4.5 |
4.5.41 |
Jul 27, 2021 |
EOL |
| 4.6 |
4.6.62 |
Oct 27, 2022 |
EOL |
| 4.7 |
4.7.60 |
Aug 24, 2022 |
EOL |
| 4.8 |
4.8.57 |
Jan 27, 2023 |
EOL |
What does Red Hat OpenShift 4.20 end of life mean?
When Red Hat OpenShift 4.20 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Red Hat OpenShift 4.20 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Red Hat OpenShift 4.22 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Red Hat OpenShift 4.20 reach end of life?
Red Hat OpenShift 4.20 reached end of life on April 21, 2027. That is 195 days remaining.
Is Red Hat OpenShift 4.20 still supported?
Yes, Red Hat OpenShift 4.20 is currently supported. The EOL date is April 21, 2027.
What should I upgrade to from Red Hat OpenShift 4.20?
The recommended upgrade from Red Hat OpenShift 4.20 is
Red Hat OpenShift 4.22 — the latest actively supported version. Check the
Red Hat OpenShift full timeline for all supported versions.
What are the security risks of running Red Hat OpenShift 4.20 past EOL?
When Red Hat OpenShift 4.20 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Red Hat OpenShift should migrate immediately or implement compensating controls.