Oracle Database 21c End of Life Date
Oracle Database 21c end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
Oracle Database 21 was released on August 13, 2021 and support is scheduled to end on July 31, 2027 — a planned supported lifespan of 6 years, in line with the 5 years and 3 months median for Oracle Database releases. It is not an LTS release; Oracle Database reserves longer patch windows for its LTS versions.
| 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 21c end of life mean?
When Oracle Database 21c 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Oracle Database 21c past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Oracle Database 26ai or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.