Oracle Database 18c End of Life Date
Oracle Database 18c end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
Oracle Database 18 was released on July 23, 2018 and support ended on June 30, 2021 — a supported lifespan of 2 years and 11 months, shorter than the 5 years and 3 months median for Oracle Database releases. It was not an LTS release; Oracle Database reserves longer patch windows for its LTS versions. It has been without security patches for 5 years and 1 month. 2 newer Oracle Database releases have shipped since.
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →| Version | Latest | EOL Date | Status |
|---|---|---|---|
| 9i Release 1 | — | Dec 31, 2003 | EOL |
| 9i Release 2 LTS | — | Jul 31, 2007 | EOL |
| 10g Release 1 LTS | — | Jan 31, 2009 | EOL |
| 10g Release 2 LTS | — | Jul 31, 2010 | EOL |
| 11g Release 1 LTS | — | Aug 31, 2012 | EOL |
| 11g Release 2 LTS | — | Jan 31, 2015 | EOL |
| 12c Release 1 LTS | — | Jul 31, 2018 | EOL |
| 12c Release 2 | — | Mar 31, 2022 | EOL |
What does Oracle Database 18c end of life mean?
When Oracle Database 18c 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 Database 18c past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Oracle Database 26ai or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.