Oracle Database 26ai · Version Status

Oracle Database 26ai End of Life Date

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

Oracle Database 26ai is actively supported. EOL date: December 31, 2031.
📅 Get reminded before Oracle Database 26ai reaches EOL on December 31, 2031 — alerts 90, 30 & 7 days out.
Google →
EOL Date
Dec 31, 2031
1970 days remaining
Latest Release
LTS release
Release Date
Sep 19, 2023
Oracle Database 26ai series
Lifecycle detail

Oracle Database 23 was released on September 19, 2023 and support is scheduled to end on December 31, 2031 — a planned supported lifespan of 8 years and 4 months, longer than the 5 years and 5 months median for Oracle Database LTS releases. It is a long-term support (LTS) release, so it carries a longer patch window than the interim releases around it.

← Oracle Database 21c All Oracle Database versions
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/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 →
All Oracle Database Versions
VersionLatestEOL DateStatus
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 26ai end of life mean?

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

Frequently Asked Questions
When does Oracle Database 26ai reach end of life?
Oracle Database 26ai reached end of life on December 31, 2031. That is 1970 days remaining.
Is Oracle Database 26ai still supported?
Yes, Oracle Database 26ai is currently supported. The EOL date is December 31, 2031.
What should I upgrade to from Oracle Database 26ai?
The recommended upgrade from Oracle Database 26ai is Oracle Database 26ai — the latest actively supported version. Check the Oracle Database full timeline for all supported versions.
What are the security risks of running Oracle Database 26ai past EOL?
When Oracle Database 26ai 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 →