Red Hat build of OpenJDK 25 · Version Status
Red Hat build of OpenJDK 25 End of Life Date
Red Hat build of OpenJDK 25 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 25 is actively supported. EOL date: December 31, 2030.
📅 Get reminded before Red Hat build of OpenJDK 25 reaches EOL on December 31, 2030 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Dec 31, 2030
1559 days remaining
Latest Release
25
Standard release
Release Date
Nov 13, 2025
Red Hat build of OpenJDK 25 series
Lifecycle detail
Red Hat build of OpenJDK 25 was released on November 13, 2025 and support is scheduled to end on December 31, 2030 — a planned supported lifespan of 5 years and 2 months, shorter than the 6 years and 2 months median for Red Hat build of OpenJDK releases. Its most recent patch is 25, published November 13, 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 →
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 25 end of life mean?
When Red Hat build of OpenJDK 25 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 25 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 25 reach end of life?
Red Hat build of OpenJDK 25 reached end of life on December 31, 2030. That is 1559 days remaining.
Is Red Hat build of OpenJDK 25 still supported?
Yes, Red Hat build of OpenJDK 25 is currently supported. The EOL date is December 31, 2030.
What should I upgrade to from Red Hat build of OpenJDK 25?
The recommended upgrade from Red Hat build of OpenJDK 25 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 25 past EOL?
When Red Hat build of OpenJDK 25 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.