Cisco Catalyst SD-WAN End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Cisco Catalyst SD-WAN versions. Dates read at the vendor's own lifecycle pages (cisco.com). Updated at every deploy.
Cisco Catalyst SD-WAN 20.12 is supported until September 30, 2027, its end-of-support date. Active support for Cisco Catalyst SD-WAN 20.12 ended on March 30, 2026; security fixes continue until that end-of-life date. It is also the next Cisco Catalyst SD-WAN version to reach end of life. 16 of 20 tracked Cisco Catalyst SD-WAN versions are past end of life; the most recent to reach it, 20.9, did so on September 30, 2026. The full Cisco Catalyst SD-WAN lifecycle, with every version's release and end-of-support date, is in the table below.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 19.1 | 19.1 | — | Aug 30, 2022 | 1518 days past EOL | EOL |
| 19.2 | 19.2 | — | Aug 30, 2022 | 1518 days past EOL | EOL |
| 19.3 | 19.3 | — | Aug 30, 2022 | 1518 days past EOL | EOL |
| 20.1 | 20.1 | — | Jul 15, 2021 | 1929 days past EOL | EOL |
| 20.3 | 20.3 | — | Sep 30, 2023 | 1122 days past EOL | EOL |
| 20.4 | 20.4 | — | Jan 28, 2022 | 1732 days past EOL | EOL |
| 20.5 | 20.5 | — | May 30, 2022 | 1610 days past EOL | EOL |
| 20.6 | 20.6 | — | Sep 30, 2024 | 756 days past EOL | EOL |
| 20.7.1 | 20.7.1 | — | Feb 7, 2023 | 1357 days past EOL | EOL |
| 20.8 | 20.8 | — | May 31, 2023 | 1244 days past EOL | EOL |
| 20.9 | 20.9 | — | Sep 30, 2026 | 26 days past EOL | EOL |
| 20.10 | 20.10 | — | Jan 27, 2024 | 1003 days past EOL | EOL |
| 20.11 | 20.11 | — | May 14, 2024 | 895 days past EOL | EOL |
| 20.12 | 20.12 | — | Sep 30, 2027 | 339 days remaining | Active |
| 20.13 | 20.13 | — | Dec 30, 2024 | 665 days past EOL | EOL |
| 20.14 | 20.14 | — | May 30, 2025 | 514 days past EOL | EOL |
| 20.15 | 20.15 | — | Sep 30, 2028 | 705 days remaining | Active |
| 20.16 | 20.16 | — | Jan 13, 2026 | 286 days past EOL | EOL |
| 20.18 | 20.18 | — | TBD | Supported | Active |
| 26.1 | 26.1 | — | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/cisco-sdwan)
Cisco Catalyst SD-WAN lifecycle status — the real story
Cisco Catalyst SD-WAN software (formerly Viptela; the release train shared by SD-WAN Manager / vManage, the Controller / vSmart, the Validator / vBond, vEdge and the IOS XE SD-WAN images) per release, from Cisco's per-release End-of-Life bulletins (18 bulletins from the SD-WAN 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 and IOS XR convention: support = End of SW Maintenance Releases, eol = End of Vulnerability/Security Support, extendedSupport = Last Date of Support; where a bulletin publishes no separate security-support milestone (20.7.1, 20.5, 20.4, 20.1, 19.2) eol mirrors End of SW Maintenance, which those bulletins define as the point Cisco stops addressing security vulnerabilities. End-of-Sale (where stated) and the announcement date are carried; endOfSale is null wherever the bulletin prints no End-of-Sale milestone, which includes 20.15, 20.12 and 20.8 (their Table 1 lists only the End-of-Life Announcement, End of SW Maintenance Releases, End of Vulnerability/Security Support and Last Date of Support; until 2026-10-09 our endOfSale for those three copied the announcement date, which Cisco never printed as an End-of-Sale date). Releases 20.18 and 26.1 have release notes but no bulletin yet and are listed as current with no dates; release dates are not stated in the bulletins and are left null.
KEV context (CISA catalog 2026.09.08): eight entries under 'Catalyst SD-WAN Manager', 'Catalyst SD-WAN', 'Catalyst SD-WAN Controller and Manager' and 'SD-WAN' (CVE-2026-20127, CVE-2026-20128, CVE-2026-20133, CVE-2026-20122, CVE-2026-20182, CVE-2026-20245, CVE-2026-20262 and CVE-2022-20775); the bare 'SD-WAN' string lacks the display name's tokens and is joined by a force override. 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.
Cisco Catalyst SD-WAN release and support pattern
Of the 20 release lines tracked, 16 are past end of life and 4 are still within support. The next scheduled end of life is 20.12 on September 30, 2027 — 339 days from this build. The longest-supported line currently published is 20.15, to September 30, 2028. Upstream also publishes an extended-support phase for 18 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 Catalyst SD-WAN security intelligence
CISA KEV history: Cisco Catalyst SD-WAN is named in CISA's Known Exploited Vulnerabilities catalog 9 times, most recently on 2026-09-30. Derived from CISA's live catalog at every build.
What does Cisco Catalyst SD-WAN end of life mean for your organization?
When a version of Cisco Catalyst SD-WAN 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 Catalyst SD-WAN 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 Catalyst SD-WAN 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 |
| Commercial extended support | Not available for Cisco Catalyst SD-WAN from the original maintainer | Third-party vendors patch some end-of-life software on a custom basis; availability depends on the specific version and source access |
| 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →