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 reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
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.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Dec 31, 2031
1880 days remaining
Latest Release
—
LTS release
Release Date
Sep 19, 2023
Oracle Database 26ai series
Where these dates come from
End of lifeDec 31, 2031Vendor's own page, read by our adapter · oracle.com · checked Nov 2, 2026high · 3 sources agree ReleaseSep 19, 2023Vendor's own page, checked by a person · oracle.com · checked Sep 10, 2026high · 2 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
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.
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
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: 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 26ai 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.
Frequently Asked Questions
When does Oracle Database 26ai reach end of life?
Oracle Database 26ai reaches end of life on December 31, 2031. That is 1880 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 vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Oracle Database should migrate immediately or implement compensating controls.