FortiManager 3.6 · Version Status
FortiManager 3.6 End of Life Date
FortiManager 3.6 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (support.fortinet.com); the source of each date is on the product page.
⚠
FortiManager 3.6 is past end of life. This version no longer receives security patches. 5728 days past EOL — migrate to a supported version immediately.
EOL Date
Feb 11, 2011
5728 days past EOL
Latest Release
3.6
Standard release
Release Date
Feb 11, 2008
FortiManager 3.6 series
Where these dates come from
| End of life | Feb 11, 2011 | Our catalog, built from the vendor pages · support.fortinet.com | medium · 1 source agrees |
| Release | Feb 11, 2008 | Our catalog, built from the vendor pages · support.fortinet.com | medium · 1 source agrees |
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
FortiManager 3.6 was released on February 11, 2008 and support ended on February 11, 2011 — a supported lifespan of 3 years, shorter than the 4 years and 6 months median for FortiManager releases. It has been without security patches for 15 years and 8 months. 13 newer FortiManager releases have shipped since.
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 →
Extended Support
Extended FortiManager 3.6 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All FortiManager Versions
| Version | Latest | EOL Date | Status |
|---|
| 3.3 |
3.3 |
Jan 31, 2010 |
EOL |
| 3.4 |
3.4 |
Mar 9, 2010 |
EOL |
| 3.5 |
3.5 |
Jul 11, 2010 |
EOL |
| → 3.6 |
3.6 |
Feb 11, 2011 |
EOL |
| 3.7 |
3.7 |
Jul 23, 2011 |
EOL |
| 4.0 |
4.0 |
Mar 12, 2012 |
EOL |
| 4.1 |
4.1 |
Sep 11, 2012 |
EOL |
| 4.2 |
4.2 |
Apr 3, 2013 |
EOL |
What does FortiManager 3.6 end of life mean?
When FortiManager 3.6 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running FortiManager 3.6 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
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 3.6 reach end of life?
FortiManager 3.6 reached end of life on February 11, 2011. This version is no longer receiving security patches.
Is FortiManager 3.6 still supported?
No. FortiManager 3.6 reached end of life on February 11, 2011 and is no longer receiving security patches.
What should I upgrade to from FortiManager 3.6?
The recommended upgrade from FortiManager 3.6 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 3.6 past EOL?
When FortiManager 3.6 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL FortiManager should migrate immediately or implement compensating controls.