FortiManager End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all FortiManager versions. Dates read at the vendor's own lifecycle pages (support.fortinet.com). Updated at every deploy.
FortiManager 8.0 is supported until October 21, 2030, its end-of-support date. Active support for FortiManager 8.0 ends on April 21, 2029. The next FortiManager version to reach end of life is 7.4, on November 15, 2028. 18 of 21 tracked FortiManager versions are past end of life; the most recent to reach it, 7.2, did so on October 11, 2026. The full FortiManager lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.3 | 3.3 | Jan 31, 2007 | Jan 31, 2010 | 6104 days past EOL | EOL |
| 3.4 | 3.4 | Mar 9, 2007 | Mar 9, 2010 | 6067 days past EOL | EOL |
| 3.5 | 3.5 | Jul 11, 2007 | Jul 11, 2010 | 5943 days past EOL | EOL |
| 3.6 | 3.6 | Feb 11, 2008 | Feb 11, 2011 | 5728 days past EOL | EOL |
| 3.7 | 3.7 | Jul 23, 2008 | Jul 23, 2011 | 5566 days past EOL | EOL |
| 4.0 | 4.0 | Mar 12, 2009 | Mar 12, 2012 | 5333 days past EOL | EOL |
| 4.1 | 4.1 | Sep 11, 2009 | Sep 11, 2012 | 5150 days past EOL | EOL |
| 4.2 | 4.2 | Apr 3, 2010 | Apr 3, 2013 | 4946 days past EOL | EOL |
| 4.3 | 4.3 | Jun 30, 2011 | Jun 30, 2014 | 4493 days past EOL | EOL |
| 5.0 | 5.0 | Nov 1, 2012 | May 1, 2017 | 3457 days past EOL | EOL |
| 5.2 | 5.2 | Aug 23, 2014 | Feb 23, 2019 | 2794 days past EOL | EOL |
| 5.4 | 5.4 | Feb 17, 2016 | Aug 17, 2020 | 2253 days past EOL | EOL |
| 5.6 | 5.6 | Jul 27, 2017 | Jan 27, 2022 | 1725 days past EOL | EOL |
| 6.0 | 6.0 | Apr 18, 2018 | Oct 18, 2022 | 1461 days past EOL | EOL |
| 6.2 | 6.2 | Apr 11, 2019 | Oct 11, 2023 | 1103 days past EOL | EOL |
| 6.4 | 6.4 | Apr 9, 2020 | Oct 9, 2024 | 739 days past EOL | EOL |
| 7.0 | 7.0 | Apr 22, 2021 | Oct 22, 2025 | 361 days past EOL | EOL |
| 7.2 | 7.2 | Apr 11, 2022 | Oct 11, 2026 | 7 days past EOL | EOL |
| 7.4 | 7.4 | May 15, 2023 | Nov 15, 2028 | 759 days remaining | Active |
| 7.6 | 7.6 | Jul 29, 2024 | Jan 29, 2030 | 1199 days remaining | Active |
| 8.0 | 8.0 | Apr 21, 2026 | Oct 21, 2030 | 1464 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/fortimanager)
FortiManager lifecycle status — the real story
FortiManager centralized-management lifecycle from Fortinet's public product life cycle portal (the same public JSON endpoint that backs support.fortinet.com/welcome/#/lifecycle; software data last updated 2026-08-24, fetched and verified 2026-09-09; the file is generated from that endpoint by tools/fortinet-lifecycle.mjs, 21 lines from 3.3 through 8.0). Milestone mapping: support = End of Engineering Support (EOES), eol = End of Support (EOS). Fortinet's stated policy is 36 months of engineering support from GA plus 18 months of 'Must Fix' support to EOS; note 7.4 and 7.6 carry EOES ~4 years after GA — longer than the written policy — matching Fortinet's 2025 support-extension announcements, so never derive these dates from the policy formula.
KEV context: CVE-2024-47575 ('FortiJump', exploited in the wild October 2024) is filed by CISA under product 'FortiManager'; CVE-2026-24858 (FortiCloud SSO authentication bypass, added 2026-01-27) is filed under 'Fortinet / Multiple Products' with FortiManager named in CISA's description and in Fortinet advisory FG-IR-26-060, and is joined by a force override (two entries as of catalog 2026.10.08). The 7.0 line passed End of Support 2025-10-22 and 7.2 reaches it 2026-10-11 — within the BOD 26-02 12-month horizon.
Lines before 5.0 (3.3-4.3) are omitted as cycles: all reached End of Support more than a decade ago; Fortinet's portal still lists them if history is needed.
FortiManager release and support pattern
Across the 21 release lines with a published release date, FortiManager has shipped a new line roughly every 1 year (median interval). A line typically stays supported for about 4.5 years from its release to its end-of-life date.
Of the 21 release lines tracked, 18 are past end of life and 3 are still within support. The newest line, 8.0, was released April 21, 2026. The next scheduled end of life is 7.4 on November 15, 2028 — 759 days from this build. The longest-supported line currently published is 8.0, to October 21, 2030.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
FortiManager security intelligence
CISA KEV history: FortiManager is named in CISA's Known Exploited Vulnerabilities catalog 2 times, most recently on 2026-01-27. Derived from CISA's live catalog at every build.
What does FortiManager end of life mean for your organization?
When a version of FortiManager 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 FortiManager 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 FortiManager 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 FortiManager versions. This is a bridge, not a permanent solution — plan your migration in parallel.
FortiManager has 18 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 FortiManager 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."