EOL.Wiki EOL.Wiki
← ← Back to all products

Red Hat Build of OpenJDK

Active
Runtimes & JDKs Latest Version: 25 Latest Release: Nov 13, 2025

Red Hat build of OpenJDK is a supported OpenJDK distribution for Red Hat Enterprise Linux customers.

Versions

7

Latest Version

25

Active Support

4

EOL

3

Lifecycle Timeline

Today
25
25
21
21
17
17
11
11
8
8
7
7
6
6
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
25Nov 13, 2025-Dec 31, 203025No
Active
21Nov 14, 2023-Dec 31, 202921.0.9.0.10-1No
Active
17Nov 11, 2021-Oct 31, 202717.0.17.0.10-1No
Active
11Oct 1, 2018-Oct 31, 202411.0.25.0.9-3No
EOL
8Oct 1, 2014-Nov 30, 20261.8.0.472.b08-1No
Active
7Mar 15, 2007-Jun 30, 20201.7.0.261-2.6.22.2No
EOL
6Mar 15, 2007-Dec 31, 20161.6.0.41-1.13.13.1No
EOL

Frequently Asked Questions

Which versions of Red Hat Build of OpenJDK have reached end of life?
The following Red Hat Build of OpenJDK versions have reached end of life and no longer receive security updates: 11, 7, 6. It is recommended to upgrade to a supported version.
Is it safe to continue using Red Hat Build of OpenJDK 11?
Red Hat Build of OpenJDK 11 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Red Hat Build of OpenJDK?
The latest version of Red Hat Build of OpenJDK is 25, released in the 25 release cycle.
How many versions of Red Hat Build of OpenJDK are currently supported?
Red Hat Build of OpenJDK currently has 4 actively supported version(s): 25, 21, 17, 8.
When does Red Hat Build of OpenJDK 25 reach end of life?
Red Hat Build of OpenJDK 25 is scheduled to reach end of life on Dec 31, 2030.
What should I do when Red Hat Build of OpenJDK reaches end of life?
When a Red Hat Build of OpenJDK version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.