Complete end-of-life dates, support windows, and security status for all Oracle Apex versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 5.1 | — | Dec 21, 2016 | Dec 1, 2021 | 1620 days past EOL | EOL |
| 18.1 | — | May 24, 2018 | May 1, 2023 | 1104 days past EOL | EOL |
| 18.2 | — | Sep 28, 2018 | Sep 1, 2023 | 981 days past EOL | EOL |
| 19.1 | — | Mar 29, 2019 | Mar 31, 2024 | 769 days past EOL | EOL |
| 19.2 | — | Nov 1, 2019 | Nov 30, 2024 | 525 days past EOL | EOL |
| 20.1 | — | Apr 23, 2020 | Dec 31, 2024 | 494 days past EOL | EOL |
| 20.2 | — | Oct 21, 2020 | Dec 31, 2024 | 494 days past EOL | EOL |
| 21.1 | — | May 12, 2021 | May 31, 2024 | 708 days past EOL | EOL |
| 21.2 | — | Nov 4, 2021 | Nov 30, 2024 | 525 days past EOL | EOL |
| 22.1 | — | May 3, 2022 | Dec 31, 2024 | 494 days past EOL | EOL |
| 22.2 | — | Nov 10, 2022 | Dec 31, 2024 | 494 days past EOL | EOL |
| 23.1 | — | May 17, 2023 | Dec 31, 2024 | 494 days past EOL | EOL |
| 23.2 | — | Nov 14, 2023 | May 31, 2026 | 22 days remaining | Warning |
| 24.1 | — | Jun 17, 2024 | Dec 31, 2026 | 236 days remaining | Active |
| 24.2 | — | Jan 15, 2025 | Jul 31, 2027 | 448 days remaining | Active |
When a Oracle Apex version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Oracle Apex should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →