Cisco ASA End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Cisco ASA versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 9.16 | 9.16 | May 26, 2021 | Nov 18, 2026 | Nov 30, 2027 Extended support |
78 days remaining | Warning |
| 9.17 | 9.17 | Dec 1, 2021 | Dec 21, 2024 | Dec 31, 2025 Extended support (ended) |
619 days past EOL | EOL |
| 9.18 | 9.18 | Jun 6, 2022 | Nov 18, 2026 | Nov 30, 2027 Extended support |
78 days remaining | Warning |
| 9.19 | 9.19 | Nov 29, 2022 | May 18, 2026 | Nov 30, 2027 Extended support |
106 days past EOL | EOL |
| 9.20 | 9.20 | Sep 7, 2023 | TBD | — | Supported | Active |
| 9.22 | 9.22 | Sep 16, 2024 | TBD | — | Supported | Active |
| 9.23 | 9.23 | Mar 5, 2025 | Sep 29, 2027 | Sep 30, 2028 Extended support |
393 days remaining | Active |
| 9.24 | 9.24 | Dec 3, 2025 | TBD | — | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/cisco-asa)
Cisco ASA lifecycle status — the real story
Cisco ASA (Adaptive Security Appliance) software runs one of the largest firewall/VPN installed bases on the internet's edge — precisely the device class CISA's Binding Operational Directive 26-02 orders federal agencies to inventory and decommission once end-of-support. Cisco does not publish a single lifecycle calendar: each software train gets its own end-of-life bulletin with a ladder of dated milestones — End-of-Life Announcement, End-of-Sale, End of Software Maintenance Releases, End of Vulnerability/Security Support, and finally the Last Date of Support, after which Cisco's own definition states “all support services for the product are unavailable, and the product becomes obsolete.”
How this page maps Cisco's milestones: our active support column is Cisco's End of Software Maintenance Releases (last engineering bug fixes); our end-of-life column is Cisco's End of Vulnerability/Security Support — the last date security fixes ship, which is the boundary that matters operationally; and our extended support column is Cisco's Last Date of Support (TAC assistance continues under contract until then, but with no fixes). One caveat: the 9.17(x) bulletin predates the security-support milestone and does not list it, so 9.17's end-of-life here conservatively uses its End of Software Maintenance date (December 21, 2024). ASA 9.17 passed its Last Date of Support on December 31, 2025 — it is obsolete by Cisco's definition.
Trains without a published EOL bulletin (9.20, 9.22, 9.24 as of September 2026) are shown as supported with no announced dates — Cisco announces each train's retirement individually, typically giving about two years from end-of-sale to the last date of support. A quirk from Cisco's own release roadmap: 9.22(1) was never released; that line began at 9.22(1.1). Release dates come from Cisco's “New Features by Release” roadmap; milestone dates from the per-train EOL bulletins linked on each row. Older trains (9.8–9.14) have their own bulletins and may be added as the catalog deepens.
Cisco ASA release and support pattern
Across the 8 release lines with a published release date, Cisco ASA has shipped a new line roughly every 6 months (median interval). A line typically stays in standard support for about 3.5 years from its release to its standard-support end date (measured on the 5 lines with both dates published).
Of the 8 release lines tracked, 2 are past end of life and 6 are still within support. The newest line, 9.24, was released December 3, 2025. The next scheduled end of life is 9.18 on November 18, 2026 — 77 days from this build. The longest-supported line currently published is 9.23, to September 29, 2027. Upstream also publishes an extended-support phase for 5 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 ASA security intelligence
CISA KEV history: Cisco ASA is named in CISA's Known Exploited Vulnerabilities catalog 11 times, most recently on 2026-08-11, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does Cisco ASA end of life mean for your organization?
When a version of Cisco ASA 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 ASA 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 ASA 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 ASA versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Cisco ASA has 2 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 ASA 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."