Cisco Secure Firewall Management Center End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Cisco Secure Firewall Management Center versions. Dates read at the vendor's own lifecycle pages (cisco.com). Updated at every deploy.
Cisco Secure Firewall Management Center 10.0 is supported, with no end-of-life or end-of-support date announced yet. The next Cisco Secure Firewall Management Center version to reach end of life is 7.2, on November 18, 2026. 6 of 12 tracked Cisco Secure Firewall Management Center versions are past end of life; the most recent to reach it, 7.3, did so on May 18, 2026. The full Cisco Secure Firewall Management Center 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 |
|---|---|---|---|---|---|
| 6.3 | 6.3 | Dec 18, 2018 | Apr 30, 2021 | 2005 days past EOL | EOL |
| 6.4 | 6.4 | Mar 3, 2020 | Feb 27, 2024 | 972 days past EOL | EOL |
| 6.6 | 6.6 | May 8, 2020 | Mar 2, 2023 | 1334 days past EOL | EOL |
| 6.7 | 6.7 | Nov 2, 2020 | Jul 9, 2022 | 1570 days past EOL | EOL |
| 7.0 | 7.0 | May 26, 2021 | Nov 18, 2026 | 23 days remaining | Warning |
| 7.1 | 7.1 | Dec 1, 2021 | Dec 21, 2024 | 674 days past EOL | EOL |
| 7.2 | 7.2 | Jun 6, 2022 | Nov 18, 2026 | 23 days remaining | Warning |
| 7.3 | 7.3 | Nov 29, 2022 | May 18, 2026 | 161 days past EOL | EOL |
| 7.4 | 7.4 | Sep 7, 2023 | TBD | Supported | Active |
| 7.6 | 7.6 | Sep 16, 2024 | TBD | Supported | Active |
| 7.7 | 7.7 | Mar 14, 2025 | Sep 29, 2027 | 338 days remaining | Active |
| 10.0 | 10.0 | Dec 23, 2025 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/cisco-fmc)
Cisco Secure Firewall Management Center lifecycle status — the real story
Cisco Secure Firewall Management Center (FMC, formerly Firepower Management Center) software trains. Cisco does not publish separate FMC software bulletins: each Threat Defense end-of-life bulletin is titled for FTD, FMC and FXOS together ('...Firepower Threat Defense (FTD) 6.4(X), Firepower Management Center (FMC) 6.4(X)...'; the 6.3, 6.4, 6.6, 6.7, 7.0, 7.1, 7.2, 7.3 and 7.7 bulletins all name the Management Center in the title, confirmed 2026-09-09), and the FMC listing page itself carries only hardware-appliance and licence notices. This file therefore mirrors the cisco-ftd trains line for line with the same milestone mapping (support = End of SW Maintenance Releases, eol = End of Vulnerability/Security Support where the bulletin has one, extendedSupport = Last Date of Support) and links the same bulletins; 7.4, 7.6 and 10.0 are current with no bulletin. Release dates are the same per-train release-notes dates the FTD file uses.
KEV context (CISA catalog 2026.09.08): CVE-2026-20131 (added 2026-03-19) and CVE-2026-20316 (added 2026-07-29) under 'Secure Firewall Management Center (FMC)', matched on the display name. The ASA/FTD joint entries are tracked on those pages. No version scoping is asserted here.
Verification: frozen manual read, as for cisco-ftd; re-verify both files together when a Threat Defense bulletin appears.
Cisco Secure Firewall Management Center release and support pattern
Across the 12 release lines with a published release date, Cisco Secure Firewall Management Center has shipped a new line roughly every 6 months (median interval). A line typically stays in standard support for about 3.1 years from its release to its standard-support end date (measured on the 9 lines with both dates published).
Of the 12 release lines tracked, 6 are past end of life and 6 are still within support. The newest line, 10.0, was released December 23, 2025. The next scheduled end of life is 7.2 on November 18, 2026 — 23 days from this build. The longest-supported line currently published is 7.7, to September 29, 2027. Upstream also publishes an extended-support phase for 9 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 Secure Firewall Management Center security intelligence
CISA KEV history: Cisco Secure Firewall Management Center is named in CISA's Known Exploited Vulnerabilities catalog 3 times, most recently on 2026-09-09, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does Cisco Secure Firewall Management Center end of life mean for your organization?
When a version of Cisco Secure Firewall Management Center 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 Secure Firewall Management Center 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 Secure Firewall Management Center 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 Secure Firewall Management Center 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 →