Redhat Build Of Openjdk End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Redhat Build Of Openjdk versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
✓Redhat Build Of Openjdk 1.8.0.472.b08-1 is actively supported. Next EOL: version 8 on November 30, 2026.
Latest Active
1.8.0.472.b08-1
8 series
Next EOL
8
Nov 30, 2026
Active Versions
4
of 7 total
EOL Versions
3
no longer patched
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
3416 days past EOL
EOL
7
1.7.0.261-2.6.22.2
Mar 15, 2007
Jun 30, 2020
2139 days past EOL
EOL
8
1.8.0.472.b08-1
Oct 1, 2014
Nov 30, 2026
205 days remaining
Active
11
11.0.25.0.9-3
Oct 1, 2018
Oct 31, 2024
555 days past EOL
EOL
17
17.0.17.0.10-1
Nov 11, 2021
Dec 31, 2027
601 days remaining
Active
21
21.0.9.0.10-1
Nov 14, 2023
Dec 31, 2029
1332 days remaining
Active
25
25
Nov 13, 2025
Dec 31, 2030
1697 days remaining
Active
What does Redhat Build Of Openjdk end of life mean for your organization?
When a Redhat Build Of Openjdk version 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 Redhat 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.
Check your full stack for EOL risk
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
What is the end-of-life date for Redhat Build Of Openjdk?
The next Redhat Build Of Openjdk version reaching EOL is 8 on November 30, 2026. See the full table above for all version EOL dates.
What is the latest supported version of Redhat Build Of Openjdk?
The latest active version of Redhat Build Of Openjdk is 1.8.0.472.b08-1. Always verify against the table above as support windows can change.
What happens when Redhat Build Of Openjdk reaches end of life?
When Redhat 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 Redhat 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 Redhat Build Of Openjdk versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.