Red Hat build of OpenJDK OpenJDK 8 (1.8) · Version Status
Red Hat build of OpenJDK OpenJDK 8 (1.8) End of Life Date
Red Hat build of OpenJDK OpenJDK 8 (1.8) 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 build of OpenJDK OpenJDK 8 (1.8) reaches end of life on November 30, 2026. Plan your migration now — 68 days remaining.
📅 Get reminded before Red Hat build of OpenJDK OpenJDK 8 (1.8) reaches EOL on November 30, 2026 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Nov 30, 2026
68 days remaining
Latest Release
1.8.0.472.b08-1
Standard release
Release Date
Oct 1, 2014
Red Hat build of OpenJDK OpenJDK 8 (1.8) series
Lifecycle detail
Red Hat build of OpenJDK 8 was released on October 1, 2014 and support is scheduled to end on November 30, 2026 — a planned supported lifespan of 12 years and 2 months, longer than the 6 years and 2 months median for Red Hat build of OpenJDK releases. Its most recent patch is 1.8.0.472.b08-1, published October 16, 2025.
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 →
Extended Support
Extended Red Hat build of OpenJDK OpenJDK 8 (1.8) support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All Red Hat build of OpenJDK Versions
| Version | Latest | EOL Date | Status |
|---|
| OpenJDK 6 (1.6) |
1.6.0.41-1.13.13.1 |
Dec 31, 2016 |
EOL |
| OpenJDK 7 (1.7) |
1.7.0.261-2.6.22.2 |
Jun 30, 2020 |
EOL |
| → OpenJDK 8 (1.8) |
1.8.0.472.b08-1 |
Nov 30, 2026 |
Warning |
| 11 |
11.0.25.0.9-3 |
Oct 31, 2024 |
EOL |
| 17 |
17.0.17.0.10-1 |
Dec 31, 2027 |
Active |
| 21 |
21.0.9.0.10-1 |
Dec 31, 2029 |
Active |
| 25 |
25 |
Dec 31, 2030 |
Active |
What does Red Hat build of OpenJDK OpenJDK 8 (1.8) end of life mean?
When Red Hat build of OpenJDK OpenJDK 8 (1.8) 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 build of OpenJDK OpenJDK 8 (1.8) past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Red Hat build of OpenJDK 25 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Red Hat build of OpenJDK OpenJDK 8 (1.8) reach end of life?
Red Hat build of OpenJDK OpenJDK 8 (1.8) reached end of life on November 30, 2026. That is 68 days remaining.
Is Red Hat build of OpenJDK OpenJDK 8 (1.8) still supported?
Red Hat build of OpenJDK OpenJDK 8 (1.8) is still supported but approaching end of life on November 30, 2026. Begin planning your migration now.
What should I upgrade to from Red Hat build of OpenJDK OpenJDK 8 (1.8)?
The recommended upgrade from Red Hat build of OpenJDK OpenJDK 8 (1.8) is
Red Hat build of OpenJDK 25 — the latest actively supported version. Check the
Red Hat build of OpenJDK full timeline for all supported versions.
What are the security risks of running Red Hat build of OpenJDK OpenJDK 8 (1.8) past EOL?
When Red Hat build of OpenJDK OpenJDK 8 (1.8) 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 build of OpenJDK should migrate immediately or implement compensating controls.