Oracle Apex End of Life Dates
other
Developers rely on Oracle Apex for building robust and scalable applications, and this platform has been a cornerstone of enterprise software development since its inception. Created to simplify the development process, Oracle Apex has been maintained by Oracle Corporation, ensuring that it remains a viable option for developers seeking to create complex applications with ease. With a history spanning multiple versions, Oracle Apex has become a staple in the development community, with many developers utilizing it to streamline their workflow and create high-quality applications.
The Oracle Apex ecosystem comprises 16 versions, with 13 of these versions having reached their end-of-life, leaving 3 active versions currently supported by Oracle Corporation. The most recent version to reach its end-of-life was 23.2, which occurred on 2026-05-31, while the next version slated for end-of-life is 24.1, scheduled to expire on 2026-12-31. This information is crucial for developers seeking to plan their upgrades and ensure that their applications remain secure and supported. By tracking these end-of-life dates, developers can proactively prepare for the transition to newer versions, mitigating potential risks and ensuring continuity.
The security landscape for Oracle Apex is currently devoid of any known Common Vulnerabilities and Exposures, with a total of 0 CVEs tracked and 0 critical CVEs reported. As a result, there is no most affected version, and the Known Exploited Vulnerabilities catalog does not currently list any Oracle Apex versions. Given this information, developers should continue to monitor the Oracle Apex ecosystem for any emerging security concerns and plan their upgrades accordingly, taking advantage of the active support provided by Oracle Corporation for the remaining supported versions to ensure the integrity and security of their applications.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 26.1 | May 14, 2026 | — | Nov 30, 2027 | in 494d | — | — | Active | |
| 24.2 | Jan 15, 2025 | — | Jul 31, 2027 | in 372d | — | — | Active | |
| 24.1 | Jun 17, 2024 | — | Dec 31, 2026 | in 160d | — | — | Active | |
| 23.2 | Nov 14, 2023 | — | May 31, 2026 | 54d ago | — | — | EOL | |
| 23.1 | May 17, 2023 | — | Dec 31, 2024 | 570d ago | — | — | EOL | |
| 22.2 | Nov 10, 2022 | — | Dec 31, 2024 | 570d ago | — | — | EOL | |
| 22.1 | May 3, 2022 | — | Dec 31, 2024 | 570d ago | — | — | EOL | |
| 21.2 | Nov 4, 2021 | — | Nov 30, 2024 | 601d ago | — | — | EOL | |
| 21.1 | May 12, 2021 | — | May 31, 2024 | 784d ago | — | — | EOL | |
| 20.2 | Oct 21, 2020 | — | Dec 31, 2024 | 570d ago | — | — | EOL | |
| 20.1 | Apr 23, 2020 | — | Dec 31, 2024 | 570d ago | — | — | EOL | |
| 19.2 | Nov 1, 2019 | — | Nov 30, 2024 | 601d ago | — | — | EOL | |
| 19.1 | Mar 29, 2019 | — | Mar 31, 2024 | 845d ago | — | — | EOL | |
| 18.2 | Sep 28, 2018 | — | Sep 1, 2023 | 1057d ago | — | — | EOL | |
| 18.1 | May 24, 2018 | — | May 1, 2023 | 1180d ago | — | — | EOL | |
| 5.1 | Dec 21, 2016 | — | Dec 1, 2021 | 1696d ago | — | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
