FortiManager 6.0 · Version Status

FortiManager 6.0 End of Life Date

FortiManager 6.0 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

FortiManager 6.0 is past end of life. This version no longer receives security patches. 1415 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 18, 2022
1415 days past EOL
Latest Release
6.0
Standard release
Release Date
Apr 18, 2018
FortiManager 6.0 series
Lifecycle detail

FortiManager 6.0 was released on April 18, 2018 and support ended on October 18, 2022 — a supported lifespan of 4 years and 6 months, in line with the 4 years and 6 months median for FortiManager releases. It has been without security patches for 3 years and 11 months. 3 newer FortiManager releases have shipped since.

← FortiManager 5.6 All FortiManager versions FortiManager 6.2 →
70 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
40/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
Recommended upgrade path
FortiManager 8.0
Latest release: 8.0 · EOL: Oct 21, 2030
View full FortiManager timeline →
Extended Support
Extended FortiManager 6.0 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All FortiManager Versions
VersionLatestEOL DateStatus
5.0 5.0 May 1, 2017 EOL
5.2 5.2 Feb 23, 2019 EOL
5.4 5.4 Aug 17, 2020 EOL
5.6 5.6 Jan 27, 2022 EOL
6.0 6.0 Oct 18, 2022 EOL
6.2 6.2 Oct 11, 2023 EOL
6.4 6.4 Oct 9, 2024 EOL
7.0 7.0 Oct 22, 2025 EOL

What does FortiManager 6.0 end of life mean?

When FortiManager 6.0 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running FortiManager 6.0 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to FortiManager 8.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does FortiManager 6.0 reach end of life?
FortiManager 6.0 reached end of life on October 18, 2022. This version is no longer receiving security patches.
Is FortiManager 6.0 still supported?
No. FortiManager 6.0 reached end of life on October 18, 2022 and is no longer receiving security patches.
What should I upgrade to from FortiManager 6.0?
The recommended upgrade from FortiManager 6.0 is FortiManager 8.0 — the latest actively supported version. Check the FortiManager full timeline for all supported versions.
What are the security risks of running FortiManager 6.0 past EOL?
When FortiManager 6.0 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL FortiManager should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →