Cisco Unified Communications Manager End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Cisco Unified Communications Manager versions. Dates read at the vendor's own lifecycle pages (cisco.com). Updated at every deploy.
Cisco Unified Communications Manager 15 is supported, with no end-of-life or end-of-support date announced yet. 19 of 20 tracked Cisco Unified Communications Manager versions are past end of life; the most recent to reach it, 14, did so on April 7, 2026. The full Cisco Unified Communications Manager lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 3.x | 3.x | — | Jul 22, 2008 | Jul 22, 2010 Extended support (ended) |
6661 days past EOL | EOL |
| 4.1 | 4.1 | — | May 15, 2009 | May 31, 2011 Extended support (ended) |
6364 days past EOL | EOL |
| 4.2 | 4.2 | — | May 15, 2009 | May 15, 2011 Extended support (ended) |
6364 days past EOL | EOL |
| 4.3 | 4.3 | — | Jan 25, 2012 | Jan 31, 2014 Extended support (ended) |
5379 days past EOL | EOL |
| 5.0 | 5.0 | — | Jun 30, 2009 | Jun 30, 2011 Extended support (ended) |
6318 days past EOL | EOL |
| 5.1 | 5.1 | — | Feb 13, 2010 | Feb 29, 2012 Extended support (ended) |
6090 days past EOL | EOL |
| 6.0 | 6.0 | — | May 2, 2010 | May 1, 2012 Extended support (ended) |
6012 days past EOL | EOL |
| 6.1 | 6.1 | — | Sep 3, 2011 | Sep 30, 2013 Extended support (ended) |
5523 days past EOL | EOL |
| 7.0 | 7.0 | — | Apr 12, 2011 | Apr 11, 2013 Extended support (ended) |
5667 days past EOL | EOL |
| 7.1 | 7.1 | — | Jun 22, 2013 | Jun 30, 2015 Extended support (ended) |
4865 days past EOL | EOL |
| 8.0 | 8.0 | — | Oct 23, 2012 | Oct 31, 2014 Extended support (ended) |
5107 days past EOL | EOL |
| 8.6 | 8.6 | — | Jul 26, 2015 | Jul 31, 2017 Extended support (ended) |
4101 days past EOL | EOL |
| 9.x | 9.x | — | Mar 31, 2017 | Dec 31, 2018 Extended support (ended) |
3487 days past EOL | EOL |
| 10.x | 10.x | — | Jul 1, 2020 | Jul 31, 2022 Extended support (ended) |
2299 days past EOL | EOL |
| 11.0 | 11.0 | — | Aug 1, 2018 | Jul 31, 2020 Extended support (ended) |
2999 days past EOL | EOL |
| 11.5 | 11.5 | — | May 31, 2022 | May 31, 2024 Extended support (ended) |
1600 days past EOL | EOL |
| 12.0 | 12.0 | — | Aug 17, 2021 | Aug 31, 2023 Extended support (ended) |
1887 days past EOL | EOL |
| 12.5 | 12.5 | — | Aug 31, 2024 | Aug 31, 2025 Extended support (ended) |
777 days past EOL | EOL |
| 14 | 14 | — | Apr 7, 2026 | Apr 30, 2027 Extended support |
193 days past EOL | EOL |
| 15 | 15 | — | TBD | — | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/cisco-ucm)
Cisco Unified Communications Manager lifecycle status — the real story
Cisco Unified Communications Manager (CUCM, formerly CallManager) per major release, from Cisco's per-release End-of-Life bulletins (19 bulletins from the CUCM EoS/EoL notice listing, read 2026-09-09 through a fetch proxy because cisco.com bot-blocks plain requests). Milestone mapping follows our Cisco ASA/FTD convention: support = End of SW Maintenance Releases, extendedSupport = Last Date of Support (application software); none of the CUCM bulletins publishes a separate End of Vulnerability/Security Support milestone, so eol mirrors End of SW Maintenance Releases, the last day Cisco ships fixes of any kind. End-of-Sale and the announcement date are carried. Version 14 has two bulletins (perpetual and Flex subscription) with identical dates; version 15 has release notes (15 through 15SU4a) but no bulletin yet and is listed as current. The 10.x bulletin notes a limited extension of maintenance for 10.5 to 2020-10-01 because of COVID-19; the table date 2020-07-01 is recorded. Release dates are not stated in the bulletins and are left null.
KEV context (CISA catalog 2026.09.08): CVE-2026-20045 (added 2026-01-21) and CVE-2026-20230 (added 2026-06-25) under 'Unified Communications Manager', matched on the display name. No version scoping is asserted here.
Verification: cisco.com is bot-blocked for plain fetches, so this file is a frozen manual read; each line links its own bulletin and the notice listing is the index to re-read.
Rule (2026-10-09): each version takes its dates from Cisco’s general End-of-Sale and End-of-Life bulletin for that version. Special-edition bulletins (JITC Certified, FIPS, government builds) carry later dates for that edition only and are never used for the main line; until 2026-10-09 the 8.6 row carried the JITC Certified bulletin’s dates (support to 2017-08-02, last support 2019-08-31) instead of the general 8.5 and 8.6 bulletin (2015-07-26 and 2017-07-31).
Cisco Unified Communications Manager release and support pattern
Of the 20 release lines tracked, 19 are past end of life and 1 is still within support. No end-of-life date is currently published for the 1 supported line. Upstream also publishes an extended-support phase for 19 lines, shown in the table above.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Cisco Unified Communications Manager security intelligence
CISA KEV history: Cisco Unified Communications Manager is named in CISA's Known Exploited Vulnerabilities catalog 2 times, most recently on 2026-06-25. Derived from CISA's live catalog at every build.
What does Cisco Unified Communications Manager end of life mean for your organization?
When a version of Cisco Unified Communications Manager 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Cisco Unified Communications Manager 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 Cisco Unified Communications Manager 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.
| Option | Best when | Watch 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.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Cisco Unified Communications Manager versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Cisco Unified Communications Manager has 19 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Cisco Unified Communications Manager is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."