Oracle APEX 18.2 · Version Status

Oracle APEX 18.2 End of Life Date

Oracle APEX 18.2 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Oracle APEX 18.2 is past end of life. This version no longer receives security patches. 1076 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 1, 2023
1076 days past EOL
Latest Release
Standard release
Release Date
Sep 28, 2018
Oracle APEX 18.2 series
Lifecycle detail

Oracle APEX 18.2 was released on September 28, 2018 and support ended on September 1, 2023 — a supported lifespan of 4 years and 11 months, longer than the 3 years and 1 month median for Oracle APEX releases. It has been without security patches for 3 years. 4 newer Oracle APEX releases have shipped since.

← Oracle APEX 18.1 All Oracle APEX versions Oracle APEX 19.1 →
50 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
40/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
Recommended upgrade path
Oracle APEX 26.1
Latest release: — · EOL: Nov 30, 2027
View full Oracle APEX timeline →
Extended Support
Extended Oracle APEX 18.2 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All Oracle APEX Versions
VersionLatestEOL DateStatus
5.1 Dec 1, 2021 EOL
18.1 May 1, 2023 EOL
18.2 Sep 1, 2023 EOL
19.1 Mar 31, 2024 EOL
19.2 Nov 30, 2024 EOL
20.1 Dec 31, 2024 EOL
20.2 Dec 31, 2024 EOL
21.1 May 31, 2024 EOL

What does Oracle APEX 18.2 end of life mean?

When Oracle APEX 18.2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Oracle APEX 18.2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Oracle APEX 26.1 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Oracle APEX 18.2 reach end of life?
Oracle APEX 18.2 reached end of life on September 1, 2023. This version is no longer receiving security patches.
Is Oracle APEX 18.2 still supported?
No. Oracle APEX 18.2 reached end of life on September 1, 2023 and is no longer receiving security patches.
What should I upgrade to from Oracle APEX 18.2?
The recommended upgrade from Oracle APEX 18.2 is Oracle APEX 26.1 — the latest actively supported version. Check the Oracle APEX full timeline for all supported versions.
What are the security risks of running Oracle APEX 18.2 past EOL?
When Oracle APEX 18.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Oracle APEX should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →