Oracle Database 10g Release 2 · Version Status

Oracle Database 10g Release 2 End of Life Date

Oracle Database 10g Release 2 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 10g Release 2 is past end of life. This version no longer receives security patches. 5913 days past EOL — migrate to a supported version immediately.
EOL Date
Jul 31, 2010
5913 days past EOL
Latest Release
—
LTS release
Release Date
Jul 11, 2005
Oracle Database 10g Release 2 series
Extended Support
Jul 31, 2013
Extended support · ended
Lifecycle detail

Oracle Database 10.2 was released on July 11, 2005 and support ended on July 31, 2010 — a supported lifespan of 5 years and 1 month, in line with the 5 years and 5 months median for Oracle Database LTS releases. It was a long-term support (LTS) release, so it received a longer patch window than the interim releases around it. It has been without security patches for 16 years and 2 months. 6 newer Oracle Database releases have shipped since.

← Oracle Database 10g Release 1 All Oracle Database versions Oracle Database 11g Release 1 →
50 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
40/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 →
Recommended upgrade path
Oracle Database 26ai
Latest release: — · EOL: Dec 31, 2031
View full Oracle Database timeline →
Extended Support
Extended Oracle Database 10g Release 2 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
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 10g Release 2 end of life mean?

When Oracle Database 10g Release 2 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 10g Release 2 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 10g Release 2 reach end of life?
Oracle Database 10g Release 2 reached end of life on July 31, 2010. This version is no longer receiving security patches.
Is Oracle Database 10g Release 2 still supported?
No. Oracle Database 10g Release 2 reached end of life on July 31, 2010 and is no longer receiving security patches.
What should I upgrade to from Oracle Database 10g Release 2?
The recommended upgrade from Oracle Database 10g Release 2 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 10g Release 2 past EOL?
When Oracle Database 10g Release 2 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.
Data from endoflife.date API · Generated at build time · How we source data →