FortiADC 8.0 · Version Status
FortiADC 8.0 End of Life Date
FortiADC 8.0 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.
✓
FortiADC 8.0 is actively supported. EOL date: November 20, 2029.
📅 Get reminded before FortiADC 8.0 reaches EOL on November 20, 2029 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
Automating this check?
GET https://api.endoflife.ai/v1/score/fortiadc/8.0 returns this version's end-of-life date, its source and the EOL Risk Score as JSON.
Get a free API key (150 requests a day, no expiry).
EOL Date
Nov 20, 2029
1098 days remaining
Latest Release
8.0
Standard release
Release Date
May 20, 2025
FortiADC 8.0 series
Where these dates come from
End of lifeNov 20, 2029Our catalog, built from the vendor pages · support.fortinet.commedium · 1 source agrees End of active supportMay 20, 2028Our catalog, built from the vendor pages · support.fortinet.commedium · 1 source agrees ReleaseMay 20, 2025Our catalog, built from the vendor pages · support.fortinet.commedium · 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
FortiADC 8.0 was released on May 20, 2025 and support is scheduled to end on November 20, 2029 — a planned supported lifespan of 4 years and 6 months, in line with the 4 years and 6 months median for FortiADC releases.
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 →
| Version | Latest | EOL Date | Status |
| 2.1 |
2.1 |
Nov 8, 2017 |
EOL |
| 3.0 |
3.0 |
Jan 19, 2018 |
EOL |
| 3.1 |
3.1 |
Jun 5, 2018 |
EOL |
| 3.2 |
3.2 |
Jul 31, 2018 |
EOL |
| 4.0 |
4.0 |
Oct 3, 2018 |
EOL |
| 4.1 |
4.1 |
Dec 9, 2018 |
EOL |
| 4.2 |
4.2 |
Jul 22, 2019 |
EOL |
| 4.3 |
4.3 |
Jan 31, 2020 |
EOL |
What does FortiADC 8.0 end of life mean?
When FortiADC 8.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: 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 FortiADC 8.0 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to FortiADC 8.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does FortiADC 8.0 reach end of life?
FortiADC 8.0 reaches end of life on November 20, 2029. That is 1098 days remaining.
Is FortiADC 8.0 still supported?
Yes, FortiADC 8.0 is currently supported. The EOL date is November 20, 2029.
What should I upgrade to from FortiADC 8.0?
The recommended upgrade from FortiADC 8.0 is
FortiADC 8.0 — the latest actively supported version. Check the
FortiADC full timeline for all supported versions.
What are the security risks of running FortiADC 8.0 past EOL?
When FortiADC 8.0 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 FortiADC should migrate immediately or implement compensating controls.