Red Hat build of OpenJDK 11 End of Life Date
Red Hat build of OpenJDK 11 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 11 was released on October 1, 2018 and support ended on October 31, 2024 — a supported lifespan of 6 years and 1 month, in line with the 6 years and 2 months median for Red Hat build of OpenJDK releases. The last patch it will ever receive is 11.0.25.0.9-3, published January 14, 2025 — 3 months after the published end-of-life date. It has been without security patches for 1 year and 11 months. 1 newer Red Hat build of OpenJDK release has shipped since.
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →| 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 11 end of life mean?
When Red Hat build of OpenJDK 11 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 11 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.