DCE · Lifecycle Status

DCE End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all DCE versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

DCE 5.0-20260131 is actively supported. Next EOL: version 5.0 on January 31, 2029.
Running an EOL version? Get matched with support options — free ↓
📅 Get reminded before DCE 5.0 reaches EOL on January 31, 2029 — alerts 90, 30 & 7 days out.
Google →
Latest Active
5.0-20260131
5.0 series
Next EOL
5.0
Jan 31, 2029
Active Versions
1
of 3 total
EOL Versions
2
no longer patched
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 →
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 201920202021202220232024202520262027202820293.04.05.0TODAY
2 versions of DCE are past end of life — security patches have stopped. Get matched with support →
All Versions
VersionLatest ReleaseRelease DateEOL DateExtended SupportDaysStatus
3.0 2021.12.30.3.0.8 Jul 15, 2018 Jul 30, 2021 Jul 30, 2023
Extended support (ended)
1836 days past EOL EOL
4.0 2022.12.15.4.0.11 Mar 31, 2020 Mar 31, 2023 Mar 31, 2025
Extended support (ended)
1227 days past EOL EOL
5.0 5.0-20260131 Jun 1, 2023 Jan 31, 2029 Jan 31, 2031
Extended support
906 days remaining Active
EOL date vs extended support. The EOL Date column is the end of standard, included support. Extended support terms vary by vendor. Check whether the programme covers you before relying on these dates.
DCE EOL status badge Live EOL badge for your README — updates automatically at every build. [![DCE EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Fdce.json)](https://endoflife.ai/dce)

What does DCE end of life mean for your organization?

When a version of DCE reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL DCE should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when DCE reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

OptionBest whenWatch out for
Move to a supported version The system will outlive the current version's support window and you can schedule the work Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits
Replace the component The project is unmaintained, or a better-supported alternative exists The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem
Buy extended support Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application A bridge, not a destination — every year purchased is a year the migration still has to happen
Document accepted risk The system is isolated, short-lived, or scheduled for retirement Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL DCE versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Get DCE Support Options

DCE has 2 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for DCE exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.

Free · No obligation · Independent — we track the dates, vendors don't pay for placement · Dates verified against vendor sources
Frequently Asked Questions
What is the end-of-life date for DCE?
The next DCE version reaching EOL is 5.0 on January 31, 2029. See the full table above for all version EOL dates.
When is the DCE support end date?
The next DCE support end date is January 31, 2029, when version 5.0 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of DCE?
The latest active version of DCE is 5.0-20260131. Always verify against the table above as support windows can change.
What happens when DCE reaches end of life?
When DCE reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of DCE?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL DCE versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →
DCE end-of-life status badge