Cisco Catalyst SD-WAN End of Life (EOL) Dates & Support Timeline

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 — 348 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.

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 Catalyst SD-WAN versions. This is a bridge, not a permanent solution — plan your migration in parallel.

Related Products