Red Hat build of OpenJDK End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Red Hat build of OpenJDK versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
⚡Red Hat build of OpenJDK 8 reaches end of life on November 30, 2026. Plan your migration now — 160 days remaining.
📅 Get reminded before Red Hat build of OpenJDK 8 reaches EOL on November 30, 2026 — alerts 90, 30 & 7 days out.
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 →
Release Cycle Timeline
■ EOL
■ Warning
■ Active
┊ Today
All Versions
Version
Latest Release
Release Date
EOL Date
Days
Status
6
1.6.0.41-1.13.13.1
Mar 15, 2007
Dec 31, 2016
3461 days past EOL
EOL
7
1.7.0.261-2.6.22.2
Mar 15, 2007
Jun 30, 2020
2184 days past EOL
EOL
8
1.8.0.472.b08-1
Oct 1, 2014
Nov 30, 2026
160 days remaining
Warning
11
11.0.25.0.9-3
Oct 1, 2018
Oct 31, 2024
600 days past EOL
EOL
17
17.0.17.0.10-1
Nov 11, 2021
Dec 31, 2027
556 days remaining
Active
21
21.0.9.0.10-1
Nov 14, 2023
Dec 31, 2029
1287 days remaining
Active
25
25
Nov 13, 2025
Dec 31, 2030
1652 days remaining
Active
What does Red Hat build of OpenJDK end of life mean for your organization?
When a version of Red Hat build of OpenJDK 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 build of OpenJDK 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 build of OpenJDK versions. This is a bridge, not a permanent solution — plan your migration in parallel.
endoflife.ai
Need Extended Support?
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
What is the end-of-life date for Red Hat build of OpenJDK?
The next Red Hat build of OpenJDK version reaching EOL is 8 on November 30, 2026. See the full table above for all version EOL dates.
When is the Red Hat build of OpenJDK support end date?
The next Red Hat build of OpenJDK support end date is November 30, 2026, when version 8 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of Red Hat build of OpenJDK?
The latest active version of Red Hat build of OpenJDK is 25. Always verify against the table above as support windows can change.
What happens when Red Hat build of OpenJDK reaches end of life?
When Red Hat build of OpenJDK reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Red Hat build of OpenJDK?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Red Hat build of OpenJDK versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.