Oracle Database End of Life Dates
other
Developers working with databases are well aware of the importance of staying up to date with the latest versions of their database management systems. Oracle Database, a proprietary multi-model database management system, has been a staple in the industry since its creation by Oracle Corporation. With a history of providing robust and scalable solutions, Oracle Database has become a go-to choice for many developers due to its ability to handle a wide range of data models. The fact that it is maintained by Oracle Corporation, a well-established and reputable company, further solidifies its position as a trusted solution.
The end-of-life landscape for Oracle Database is a critical aspect that developers need to be aware of, as using outdated versions can pose significant security risks. Currently, out of the 12 versions that exist, 9 have reached their end-of-life, leaving only 3 active versions. The next version to expire is version 21, which is set to reach its end-of-life on 2027-07-31. This gives developers ample time to plan and upgrade to a newer version. It is also worth mentioning that the last version to reach its end-of-life was version 12.2, which expired on 2022-03-31.
When it comes to security, Oracle Database has a clean slate, with 0 CVEs tracked and 0 critical CVEs. This is a testament to the robust security measures in place. Since there are no CVEs, there is no most affected version. Additionally, with no known vulnerabilities, Oracle Database is not listed on the Known Exploited Vulnerabilities catalog. Despite this, developers should still prioritize upgrading to the latest versions to ensure they have access to the latest features and security patches. By doing so, they can ensure the integrity and security of their databases, and take advantage of the latest advancements in database technology.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 23 LTS | Sep 19, 2023 | — | Dec 31, 2031 | in 1986d | — | — | Active | |
| 21 | Aug 13, 2021 | — | Jul 31, 2027 | in 372d | — | — | Active | |
| 19 LTS | Apr 25, 2019 | — | Dec 31, 2029 | in 1256d | — | — | Active | |
| 18 | Jul 23, 2018 | — | Jun 30, 2021 | 1850d ago | — | — | EOL | |
| 12.2 | Mar 1, 2017 | — | Mar 31, 2022 | 1576d ago | — | — | EOL | |
| 12.1 LTS | Jun 25, 2013 | — | Jul 31, 2018 | 2915d ago | — | — | EOL | |
| 11.2 LTS | Sep 1, 2009 | — | Jan 31, 2015 | 4192d ago | — | — | EOL | |
| 11.1 LTS | Aug 9, 2007 | — | Aug 31, 2012 | 5075d ago | — | — | EOL | |
| 10.2 LTS | Jul 11, 2005 | — | Jul 31, 2010 | 5837d ago | — | — | EOL | |
| 10.1 LTS | Sep 8, 2003 | — | Jan 31, 2009 | 6383d ago | — | — | EOL | |
| 9.2 LTS | May 1, 2002 | — | Jul 31, 2007 | 6933d ago | — | — | EOL | |
| 9.0 | Jun 1, 2001 | — | Dec 31, 2003 | 8241d ago | — | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
