FortiADC End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all FortiADC versions. Dates read at the vendor's own lifecycle pages (support.fortinet.com). Updated at every deploy.
FortiADC 8.0 is supported until November 20, 2029, its end-of-support date. Active support for FortiADC 8.0 ends on May 20, 2028. The next FortiADC version to reach end of life is 7.1, on February 1, 2027. 22 of 27 tracked FortiADC versions are past end of life; the most recent to reach it, 7.0, did so on August 1, 2026. The full FortiADC 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 |
|---|---|---|---|---|---|
| 2.1 | 2.1 | May 8, 2013 | Nov 8, 2017 | 3265 days past EOL | EOL |
| 3.0 | 3.0 | Jul 19, 2013 | Jan 19, 2018 | 3193 days past EOL | EOL |
| 3.1 | 3.1 | Dec 5, 2013 | Jun 5, 2018 | 3056 days past EOL | EOL |
| 3.2 | 3.2 | Jan 31, 2014 | Jul 31, 2018 | 3000 days past EOL | EOL |
| 4.0 | 4.0 | Apr 3, 2014 | Oct 3, 2018 | 2936 days past EOL | EOL |
| 4.1 | 4.1 | Jun 9, 2014 | Dec 9, 2018 | 2869 days past EOL | EOL |
| 4.2 | 4.2 | Jan 22, 2015 | Jul 22, 2019 | 2644 days past EOL | EOL |
| 4.3 | 4.3 | Jul 31, 2015 | Jan 31, 2020 | 2451 days past EOL | EOL |
| 4.4 | 4.4 | Jan 16, 2016 | Jul 16, 2020 | 2284 days past EOL | EOL |
| 4.5 | 4.5 | Apr 16, 2016 | Oct 16, 2020 | 2192 days past EOL | EOL |
| 4.6 | 4.6 | Sep 21, 2016 | Mar 21, 2021 | 2036 days past EOL | EOL |
| 4.7 | 4.7 | Jan 23, 2017 | Jul 23, 2021 | 1912 days past EOL | EOL |
| 4.8 | 4.8 | Jun 15, 2017 | Dec 15, 2021 | 1767 days past EOL | EOL |
| 5.0 | 5.0 | Feb 1, 2018 | Aug 1, 2022 | 1538 days past EOL | EOL |
| 5.1 | 5.1 | Jul 9, 2018 | Jan 9, 2023 | 1377 days past EOL | EOL |
| 5.2 | 5.2 | Dec 29, 2018 | Jun 29, 2023 | 1206 days past EOL | EOL |
| 5.3 | 5.3 | Jul 15, 2019 | Jan 15, 2024 | 1006 days past EOL | EOL |
| 5.4 | 5.4 | Feb 4, 2020 | Aug 4, 2024 | 804 days past EOL | EOL |
| 6.0 | 6.0 | Jul 27, 2020 | Jan 27, 2025 | 628 days past EOL | EOL |
| 6.1 | 6.1 | Dec 30, 2020 | Jun 30, 2025 | 474 days past EOL | EOL |
| 6.2 | 6.2 | Aug 4, 2021 | Feb 4, 2026 | 255 days past EOL | EOL |
| 7.0 | 7.0 | Feb 1, 2022 | Aug 1, 2026 | 77 days past EOL | EOL |
| 7.1 | 7.1 | Aug 1, 2022 | Feb 1, 2027 | 107 days remaining | Warning |
| 7.2 | 7.2 | Feb 3, 2023 | Aug 3, 2027 | 290 days remaining | Active |
| 7.4 | 7.4 | Jul 10, 2023 | Jan 10, 2028 | 450 days remaining | Active |
| 7.6 | 7.6 | Jul 17, 2024 | Jan 17, 2029 | 823 days remaining | Active |
| 8.0 | 8.0 | May 20, 2025 | Nov 20, 2029 | 1130 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/fortiadc)
FortiADC lifecycle status — the real story
FortiADC application delivery controller 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 27 published software lines included (2.1 through 8.0); hardware appliance rows on the same endpoint are skipped, they belong to a hardware platform file. 22 of the 27 lines are past End of Support as of the fetch date.
KEV context (CISA catalog 2026.09.08, matched on the display name): CVE-2018-13374 (FortiOS and FortiADC, added 2022-09-08). No version scoping is asserted here; the affected lines are whatever Fortinet's advisory says, and the score uses the catalog join only.
FortiADC release and support pattern
Across the 27 release lines with a published release date, FortiADC has shipped a new line roughly every 6 months (median interval). A line typically stays supported for about 4.5 years from its release to its end-of-life date.
Of the 27 release lines tracked, 22 are past end of life and 5 are still within support. The newest line, 8.0, was released May 20, 2025. The next scheduled end of life is 7.1 on February 1, 2027 — 107 days from this build. The longest-supported line currently published is 8.0, to November 20, 2029.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
FortiADC security intelligence
CISA KEV history: FortiADC is named in CISA's Known Exploited Vulnerabilities catalog 1 time, most recently on 2022-09-08, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does FortiADC end of life mean for your organization?
When a version of FortiADC 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL FortiADC 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 FortiADC 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 FortiADC versions. This is a bridge, not a permanent solution — plan your migration in parallel.
FortiADC has 22 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 FortiADC 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."