Cisco AnyConnect End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Cisco AnyConnect versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Every tracked Cisco AnyConnect version is past end of life; the most recent to reach it, 4.x, did so on March 31, 2024. The full Cisco AnyConnect 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 |
|---|---|---|---|---|---|---|
| 2.5 | 2.5 | — | Jun 22, 2013 | Jun 30, 2015 Extended support (ended) |
4827 days past EOL | EOL |
| 3.x | 3.x | — | Mar 1, 2016 | Mar 31, 2018 Extended support (ended) |
3844 days past EOL | EOL |
| 4.x | 4.x | — | Mar 31, 2024 | Mar 31, 2027 Extended support |
892 days past EOL | EOL |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/cisco-anyconnect)
Cisco AnyConnect lifecycle status — the real story
Cisco AnyConnect Secure Mobility Client (the VPN client; succeeded by Cisco Secure Client 5) per major line, from Cisco's End-of-Life bulletins on the AnyConnect notice listing (read 2026-09-09 through a fetch proxy because cisco.com bot-blocks plain requests). Mapping follows our Cisco convention: support = End of SW Maintenance Releases (for 3.x Cisco's wording is 'software maintenance will not be available beyond March 1, 2016'), extendedSupport = Last Date of Support / end of application software support; no AnyConnect bulletin publishes a separate security-support milestone, so eol mirrors the end of software maintenance, the last day Cisco shipped fixes. The 4.x bulletin (announced 2023-05-30) names Cisco Secure Client as the replacement and says eligible customers upgrade at no charge; 4.x application support runs to 2027-03-31. There is no current AnyConnect line: the product was retired in favour of Secure Client, which is not tracked here. Release dates are not stated in the bulletins and are left null. The Symbian and Windows Mobile client bulletins are platform retirements, not software lines, and are left out.
KEV context (CISA catalog 2026.09.08): CVE-2020-3153 and CVE-2020-3433 under 'AnyConnect Secure' (both added 2022-10-24, Windows client privilege-escalation flaws), 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.
Cisco AnyConnect release and support pattern
Of the 3 release lines tracked, 3 are past end of life and 0 are still within support. Upstream also publishes an extended-support phase for 3 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 AnyConnect security intelligence
CISA KEV history: Cisco AnyConnect is named in CISA's Known Exploited Vulnerabilities catalog 2 times, most recently on 2022-10-24, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does Cisco AnyConnect end of life mean for your organization?
When a version of Cisco AnyConnect 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 Cisco AnyConnect 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 AnyConnect 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 AnyConnect versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Cisco AnyConnect has 3 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 AnyConnect 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."