Complete end-of-life dates, support windows, and security status for all Fortios versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 6.0 | — | Mar 29, 2018 | Sep 29, 2022 | 1318 days past EOL | EOL |
| 6.2 | — | Mar 28, 2019 | Sep 28, 2023 | 954 days past EOL | EOL |
| 6.4 | — | Mar 31, 2020 | Sep 30, 2024 | 586 days past EOL | EOL |
| 7.0 | — | Mar 30, 2021 | Sep 30, 2025 | 221 days past EOL | EOL |
| 7.2 | — | Mar 31, 2022 | Sep 30, 2026 | 144 days remaining | Warning |
| 7.4 | — | May 11, 2023 | Nov 11, 2028 | 917 days remaining | Active |
| 7.6 | — | Jul 25, 2024 | Jan 25, 2030 | 1357 days remaining | Active |
| 8.0 | — | Apr 21, 2026 | Oct 21, 2030 | 1626 days remaining | Active |
When a Fortios version 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 Fortios 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →