Cisco IOS XR End of Life (EOL) Dates & Support Timeline

Cisco IOS XR lifecycle status — the real story

Cisco IOS XR, the carrier and core routing OS on the ASR 9000, NCS 540/560/5500/6000, Cisco 8000, XRv 9000 and XRd platforms, modelled per software release train from Cisco's own per-release End-of-Sale/End-of-Life bulletins (42 bulletins from the IOS XR EoS/EoL notice listing, read 2026-09-09; the 2006 bulletin for 3.2 has no readable milestone table and is left out). Milestone mapping follows our Cisco ASA and FTD convention: support = End of SW Maintenance Releases, eol = End of Vulnerability/Security Support, extendedSupport = Last Date of Support; End-of-Sale and the announcement date are carried as extra fields. Where a bulletin splits SW maintenance into Standard and Extended Maintenance Release dates (3.3-3.4, 3.6, 4.2, 4.3, 5.0, 5.1, 5.3, 6.0, 6.4, 6.5, 6.6) the later Extended date is used, the last day Cisco shipped any maintenance for the train. Bulletins for 3.9 and 6.0 publish no separate security-support milestone; for those eol mirrors End of SW Maintenance.

Release dates are not stated in the bulletins and Cisco's release-notes index is undated, so releaseDate is null on every line rather than estimated. Releases 25.3, 25.4 and 26.1 have release notes but no EoL bulletin yet and are listed as current with no dates. Cisco's lifecycle statement: a Standard Maintenance Release is supported 12 months from End of Sale and an Extended Maintenance Release 24 months from End of Sale.

KEV context (CISA catalog 2026.09.08): CISA files IOS XR entries under Cisco's 'IOS XR' product string (CVE-2022-20821 among them); the join is by display name and no version scoping is asserted here. Classic IOS and IOS XE are separate products (IOS XE is tracked on its own page).

Verification: cisco.com is bot-blocked for plain fetches (Akamai), 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 IOS XR release and support pattern

Of the 45 release lines tracked, 32 are past end of life and 13 are still within support. The next scheduled end of life is 7.8 on November 30, 2026 — 79 days from this build. The longest-supported line currently published is 25.2, to June 18, 2029. Upstream also publishes an extended-support phase for 42 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 IOS XR security intelligence

CISA KEV history: Cisco IOS XR is named in CISA's Known Exploited Vulnerabilities catalog 9 times, most recently on 2023-05-19. Derived from CISA's live catalog at every build.

What does Cisco IOS XR end of life mean for your organization?

When a version of Cisco IOS XR 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 IOS XR 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 IOS XR 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 IOS XR versions. This is a bridge, not a permanent solution — plan your migration in parallel.

Related Products