Oracle Database 19 · Version Status

Oracle Database 19 End of Life Date

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

Oracle Database 19 is actively supported. EOL date: December 31, 2029.
EOL Date
Dec 31, 2029
1332 days remaining
Latest Release
LTS release
Release Date
Apr 25, 2019
Oracle Database 19 series
← Oracle Database 18 All Oracle Database versions Oracle Database 21 →
All Oracle Database Versions
VersionLatestEOL DateStatus
9.0 Dec 31, 2003 EOL
9.2 LTS Jul 31, 2007 EOL
10.1 LTS Jan 31, 2009 EOL
10.2 LTS Jul 31, 2010 EOL
11.1 LTS Aug 31, 2012 EOL
11.2 LTS Jan 31, 2015 EOL
12.1 LTS Jul 31, 2018 EOL
12.2 Mar 31, 2022 EOL

What does Oracle Database 19 end of life mean?

When Oracle Database 19 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 19 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

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

Frequently Asked Questions
When does Oracle Database 19 reach end of life?
Oracle Database 19 reached end of life on December 31, 2029. That is 1332 days remaining.
Is Oracle Database 19 still supported?
Yes, Oracle Database 19 is currently supported. The EOL date is December 31, 2029.
What should I upgrade to from Oracle Database 19?
The recommended upgrade from Oracle Database 19 is Oracle Database 23 — the latest actively supported version. Check the Oracle Database full timeline for all supported versions.
What are the security risks of running Oracle Database 19 past EOL?
When Oracle Database 19 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 Database should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →