Oracle Database · Lifecycle Status

Oracle Database End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Oracle Database versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Oracle Database 19 is actively supported. Next EOL: version 21 on July 31, 2027.
Latest Active
19
19 series
Next EOL
21
Jul 31, 2027
Active Versions
3
of 12 total
EOL Versions
9
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20022003200420052006200720082009201020112012201320142015201620172018201920202021202220232024202520262027202820292030203120329.09.210.110.211.111.212.112.218192123TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
9.0 Jun 1, 2001 Dec 31, 2003 8165 days past EOL EOL
9.2 LTS May 1, 2002 Jul 31, 2007 6857 days past EOL EOL
10.1 LTS Sep 8, 2003 Jan 31, 2009 6307 days past EOL EOL
10.2 LTS Jul 11, 2005 Jul 31, 2010 5761 days past EOL EOL
11.1 LTS Aug 9, 2007 Aug 31, 2012 4999 days past EOL EOL
11.2 LTS Sep 1, 2009 Jan 31, 2015 4116 days past EOL EOL
12.1 LTS Jun 25, 2013 Jul 31, 2018 2839 days past EOL EOL
12.2 Mar 1, 2017 Mar 31, 2022 1500 days past EOL EOL
18 Jul 23, 2018 Jun 30, 2021 1774 days past EOL EOL
19 LTS Apr 25, 2019 Dec 31, 2029 1332 days remaining Active
21 Aug 13, 2021 Jul 31, 2027 448 days remaining Active
23 LTS Sep 19, 2023 Dec 31, 2031 2062 days remaining Active

What does Oracle Database end of life mean for your organization?

When a Oracle Database 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 Database 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Oracle Database?
The next Oracle Database version reaching EOL is 21 on July 31, 2027. See the full table above for all version EOL dates.
What is the latest supported version of Oracle Database?
The latest active version of Oracle Database is 19. Always verify against the table above as support windows can change.
What happens when Oracle Database reaches end of life?
When Oracle Database reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Oracle Database?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Oracle Database versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →