VA Technical Reference Model v 25.12

Java Runtime Environment (JRE) - Oracle

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	The Java Runtime Environment (JRE) - Oracle contains the Java virtual machine, runtime class libraries, and Java application launcher that are necessary to run programs written in the Java programming language. While this program contains everything required to run Java applications on the user`s system, this product is not a development environment and does not contain development utilities such as compilers or debuggers. The Java Platform, Standard Edition Runtime Environment (JRE), is intended for software developers and vendors to redistribute with their applications. As of this writing, Oracle has no plans to release a separate JRE for Java 11 and later and users will be required to install the full Oracle JDK to support Java 11 and beyond. NOTE: This entry only covers the Oracle professional versions of Java. This entry does NOT cover or include approvals for OpenJDK Java. OpenJDK has its own TRM entry and users should consult that entry for decisions on OpenJDK.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v25.11
Decision Date:	11/14/2025 at 01:36:24 UTC
Aliases:	Java Runtime Environment, JRE Oracle, Java Platform, Standard Edition Runtime Environment (JRE)
Introduced By:	Enterprise Program Management Office (EPMO) TRM Team
Vendor Name:	Oracle

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Major versions and minor versions of that Major released on or after 09/14/2022 are NOT EXEMPT. Major Versions released before 09/14/2022 are EXEMPT as well as minor versions of that Major regardless of release date.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
4.x	02/06/2002		10/30/2008
5.x	09/30/2004		10/30/2009
6u1-9	05/07/2007
6u10	10/15/2008
6u11-34	12/03/2008
6u35	08/30/2012
6u36-41	02/19/2013
6u43	03/04/2013
6u45	04/16/2013
6u51	06/18/2013
6u52-6u201			09/30/2018
6u211			12/31/2018
7 Support Timeline	01/01/2013		07/31/2022
7u1-17	03/04/2013
7u25	06/18/2013
7u40	09/10/2013
7u45	10/15/2013
7u51-101	01/14/2014
7u201	08/16/2018	01/15/2019	04/16/2019
7u211	01/14/2019	04/16/2019
7u221/222	04/16/2019
7u231/232	07/16/2019	10/16/2019	10/16/2019
7u241/242	10/15/2019	01/15/2020	01/15/2020
7u251/252	01/15/2020	04/15/2020	04/15/2020
7u261/262	04/15/2020	07/15/2020	07/15/2020
7u271/272	07/15/2020	10/15/2020	10/15/2020
7u281/282	10/15/2020	01/15/2021	01/15/2021
7u291/292	01/13/2021	04/15/2021	04/15/2021
7u301/302	04/13/2021	07/15/2021	07/15/2021
7u311/312	07/12/2021	10/15/2021	10/15/2021
8 Support Timeline	03/19/2014	01/31/2019	03/31/2025
8u5	04/16/2014
7u341/342 (EOL)		07/22/2022	07/22/2022
7u351/352 (EOL)		07/22/2022	07/22/2022
7u321/322	10/15/2021	01/15/2022	01/15/2022
7u331/332	01/15/2022	04/15/2022	04/15/2022
8u11	07/16/2014
8u20	08/20/2014
8u25	10/15/2014
8u31	01/21/2015
8u40	03/03/2015
8u45	04/14/2015
8u51	07/14/2015
8u60	08/18/2015
8u65	10/20/2015
8u66	10/20/2015
8u121	01/17/2017
8u71	01/19/2016
8u72	01/19/2016
8u73	02/05/2016
8u74	02/05/2016
8u77	03/31/2016
8u91	04/30/2016
8u92	04/30/2016
8u101	07/19/2016
8u102	07/19/2016
8u121	01/17/2017
8u131	04/01/2017
8u144	08/01/2017
8u151	10/01/2017
8u152
8u161	01/16/2018
8u171	04/17/2018	01/31/2019
8u181	07/17/2018	01/31/2019	01/15/2019
8u191	10/16/2018	01/15/2019	04/16/2019
8u201	01/15/2019	04/16/2019
8u202	01/15/2019	04/16/2019
8u211	04/16/2019	07/15/2019
8u212	04/16/2019	07/15/2019
8u221/222	07/16/2019	10/16/2019	10/16/2019
8u231/232	10/15/2019	01/15/2020	01/15/2020
8u241/242	01/15/2020	04/15/2020	04/15/2020
8u251/252	04/15/2020	07/15/2020	07/15/2020
8u261/262	07/15/2020	10/15/2020	10/15/2020
8u271/272	10/15/2020	01/15/2021	01/15/2021
8u281/282	01/15/2021	04/15/2021	04/15/2021
8u291/292	04/13/2021	07/15/2021	07/15/2021
8u301/302	07/12/2021	10/15/2021	10/15/2021
8u311/312	10/15/2021	01/15/2022	01/15/2022
8u331/332	04/15/2022	07/15/2022	07/15/2022
8u321/322	01/15/2022	04/15/2022	04/15/2022
8u341/342		10/15/2022	10/15/2022
8u351/352		01/15/2023	01/15/2023
8u361/362	01/17/2023	04/15/2023	04/15/2023
8u371/372	04/20/2023	07/15/2023	07/15/2023
8u381/382	07/15/2023	10/15/2023	10/15/2023
8u391/392		01/15/2024	01/15/2024
8u401	01/16/2024
8u410
8u411	04/16/2024
8u421	07/16/2024
8u431	10/16/2024
8u441	01/21/2025
8u451	04/15/2025
8u461	07/15/2025
8u471	10/21/2025
9 Support Timeline	09/01/2017	03/31/2018	03/31/2018
9.x	09/01/2017	03/31/2018	03/31/2018
10 Support Timeline	03/01/2018	09/30/2018	09/30/2018
10.x	03/01/2018	09/30/2018	09/30/2018
19.0.1	10/18/2022
20.x	03/21/2023	09/30/2023	09/30/2023
25.x	09/13/2025

Current Decision Matrix (10/28/2025)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VAIT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized w/ Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Authorized w/ Constraints (POA&M): This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Authorized w/ Constraints (DIVEST): VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past

CY2025

CY2026

CY2027

Future>

Release

4.x