FortiAnalyzer End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all FortiAnalyzer versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
FortiAnalyzer 8.0 is supported until October 21, 2030, its end-of-support date. Active support for FortiAnalyzer 8.0 ends on April 21, 2029; security fixes continue until that end-of-life date. The next FortiAnalyzer version to reach end of life is 7.2, on October 11, 2026. 17 of 21 tracked FortiAnalyzer versions are past end of life; the most recent to reach it, 7.0, did so on October 22, 2025. The full FortiAnalyzer 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 | Oct 2, 2006 | Oct 2, 2009 | 6186 days past EOL | EOL |
| 3.4 | 3.4 | Jan 12, 2007 | Jan 12, 2010 | 6084 days past EOL | EOL |
| 3.5 | 3.5 | Jul 12, 2007 | Jul 12, 2010 | 5903 days past EOL | EOL |
| 3.6 | 3.6 | Feb 4, 2008 | Feb 4, 2011 | 5696 days past EOL | EOL |
| 3.7 | 3.7 | Aug 6, 2008 | Aug 6, 2011 | 5513 days past EOL | EOL |
| 4.0 | 4.0 | Feb 25, 2009 | Feb 25, 2012 | 5310 days past EOL | EOL |
| 4.1 | 4.1 | Aug 24, 2009 | Aug 24, 2012 | 5129 days past EOL | EOL |
| 4.2 | 4.2 | Apr 7, 2010 | Apr 7, 2013 | 4903 days past EOL | EOL |
| 4.3 | 4.3 | Jun 30, 2011 | Jun 30, 2014 | 4454 days past EOL | EOL |
| 5.0 | 5.0 | Nov 1, 2012 | May 1, 2017 | 3418 days past EOL | EOL |
| 5.2 | 5.2 | Sep 4, 2014 | Mar 4, 2019 | 2746 days past EOL | EOL |
| 5.4 | 5.4 | Feb 17, 2016 | Aug 17, 2020 | 2214 days past EOL | EOL |
| 5.6 | 5.6 | Jul 27, 2017 | Jan 27, 2022 | 1686 days past EOL | EOL |
| 6.0 | 6.0 | Apr 18, 2018 | Oct 18, 2022 | 1422 days past EOL | EOL |
| 6.2 | 6.2 | Apr 11, 2019 | Oct 11, 2023 | 1064 days past EOL | EOL |
| 6.4 | 6.4 | Apr 9, 2020 | Oct 9, 2024 | 700 days past EOL | EOL |
| 7.0 | 7.0 | Apr 22, 2021 | Oct 22, 2025 | 322 days past EOL | EOL |
| 7.2 | 7.2 | Apr 11, 2022 | Oct 11, 2026 | 32 days remaining | Warning |
| 7.4 | 7.4 | May 15, 2023 | Nov 15, 2028 | 798 days remaining | Active |
| 7.6 | 7.6 | Jul 29, 2024 | Jan 29, 2030 | 1238 days remaining | Active |
| 8.0 | 8.0 | Apr 21, 2026 | Oct 21, 2030 | 1503 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/fortianalyzer)
FortiAnalyzer lifecycle status — the real story
FortiAnalyzer log and analytics management plane lifecycle from Fortinet's public product life cycle portal (same verified endpoint and mapping as FortiManager and FortiProxy: releaseDate = GA, support = End of Engineering Support, eol = End of Support; generated by tools/fortinet-lifecycle.mjs, fetched 2026-09-08). All 21 published software lines included (3.3 through 8.0); hardware appliance rows on the same endpoint are skipped, they belong to a hardware platform file. 17 of the 21 lines are past End of Support as of the fetch date.
KEV context: no CISA catalog entry names FortiAnalyzer as of catalogVersion 2026.09.08; the risk score for this product carries no KEV factor until the catalog does.
FortiAnalyzer release and support pattern
Across the 21 release lines with a published release date, FortiAnalyzer 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, 17 are past end of life and 4 are still within support. The newest line, 8.0, was released April 21, 2026. The next scheduled end of life is 7.2 on October 11, 2026 — 32 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.
What does FortiAnalyzer end of life mean for your organization?
When a version of FortiAnalyzer 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 FortiAnalyzer 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 FortiAnalyzer 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 FortiAnalyzer versions. This is a bridge, not a permanent solution — plan your migration in parallel.
FortiAnalyzer has 17 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 FortiAnalyzer 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."