FortiWeb End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all FortiWeb versions. Dates read at the vendor's own lifecycle pages (support.fortinet.com). Updated at every deploy.
FortiWeb 8.0 is supported until January 28, 2030, its end-of-support date. Active support for FortiWeb 8.0 ends on July 28, 2028. The next FortiWeb version to reach end of life is 7.2, on June 16, 2027. 24 of 28 tracked FortiWeb versions are past end of life; the most recent to reach it, 7.0, did so on July 19, 2026. The full FortiWeb 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 |
|---|---|---|---|---|---|
| 3.1 | 3.1 | Apr 20, 2009 | Apr 20, 2012 | 5302 days past EOL | EOL |
| 3.2 | 3.2 | Jun 4, 2009 | Jun 4, 2012 | 5257 days past EOL | EOL |
| 3.3 | 3.3 | Sep 3, 2009 | Sep 3, 2012 | 5166 days past EOL | EOL |
| 4.0 | 4.0 | Mar 12, 2010 | Mar 12, 2013 | 4976 days past EOL | EOL |
| 4.1 | 4.1 | Aug 3, 2010 | Aug 3, 2013 | 4832 days past EOL | EOL |
| 4.2 | 4.2 | Feb 1, 2011 | Feb 1, 2014 | 4650 days past EOL | EOL |
| 4.3 | 4.3 | Aug 1, 2011 | Aug 1, 2014 | 4469 days past EOL | EOL |
| 4.4 | 4.4 | Jun 22, 2012 | Jun 22, 2015 | 4144 days past EOL | EOL |
| 5.0 | 5.0 | May 17, 2013 | Nov 17, 2017 | 3265 days past EOL | EOL |
| 5.1 | 5.1 | Jan 20, 2014 | Jul 20, 2017 | 3385 days past EOL | EOL |
| 5.2 | 5.2 | Apr 22, 2014 | Nov 1, 2017 | 3281 days past EOL | EOL |
| 5.3 | 5.3 | Sep 2, 2014 | Mar 2, 2018 | 3160 days past EOL | EOL |
| 5.4 | 5.4 | Aug 14, 2015 | Aug 14, 2018 | 2995 days past EOL | EOL |
| 5.5 | 5.5 | Dec 15, 2015 | Dec 15, 2018 | 2872 days past EOL | EOL |
| 5.6 | 5.6 | Sep 26, 2016 | Sep 26, 2019 | 2587 days past EOL | EOL |
| 5.7 | 5.7 | Jan 18, 2017 | Jul 18, 2021 | 1926 days past EOL | EOL |
| 5.8 | 5.8 | Apr 27, 2017 | Oct 27, 2021 | 1825 days past EOL | EOL |
| 5.9 | 5.9 | Mar 20, 2018 | Sep 20, 2022 | 1497 days past EOL | EOL |
| 6.0 | 6.0 | May 23, 2018 | Nov 23, 2022 | 1433 days past EOL | EOL |
| 6.1 | 6.1 | Mar 27, 2019 | Sep 27, 2023 | 1125 days past EOL | EOL |
| 6.2 | 6.2 | Sep 30, 2019 | Mar 30, 2024 | 940 days past EOL | EOL |
| 6.3 | 6.3 | Jan 21, 2020 | Jul 21, 2024 | 827 days past EOL | EOL |
| 6.4 | 6.4 | Jul 2, 2021 | Oct 1, 2023 | 1121 days past EOL | EOL |
| 7.0 | 7.0 | Jan 19, 2022 | Jul 19, 2026 | 99 days past EOL | EOL |
| 7.2 | 7.2 | Dec 16, 2022 | Jun 16, 2027 | 233 days remaining | Active |
| 7.4 | 7.4 | Jul 25, 2023 | Jan 25, 2028 | 456 days remaining | Active |
| 7.6 | 7.6 | Jun 25, 2024 | Dec 25, 2028 | 791 days remaining | Active |
| 8.0 | 8.0 | Jul 28, 2025 | Jan 28, 2030 | 1190 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/fortiweb)
FortiWeb lifecycle status — the real story
FortiWeb web application firewall 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 28 published software lines included (3.1 through 8.0); hardware appliance rows on the same endpoint are skipped, they belong to a hardware platform file. 24 of the 28 lines are past End of Support as of the fetch date.
KEV context (CISA catalog 2026.09.08, matched on the display name): CVE-2025-58034 (FortiWeb, added 2025-11-18); CVE-2025-64446 (FortiWeb, added 2025-11-14); CVE-2025-25257 (FortiWeb, added 2025-07-18). Two more are filed under 'Fortinet / Multiple Products' and joined by a force override because Fortinet's advisories list FortiWeb as affected: CVE-2025-59718 (FG-IR-25-647, added 2025-12-16) and CVE-2026-24858 (FG-IR-26-060, added 2026-01-27); five in all as of catalog 2026.10.08. CVE-2024-23113 is not joined: CISA's description names FortiWeb but Fortinet's advisory FG-IR-24-029 does not. No version scoping is asserted here; the affected lines are whatever Fortinet's advisory says, and the score uses the catalog join only.
FortiWeb release and support pattern
Across the 28 release lines with a published release date, FortiWeb has shipped a new line roughly every 6 months (median interval). A line typically stays supported for about 3.5 years from its release to its end-of-life date.
Of the 28 release lines tracked, 24 are past end of life and 4 are still within support. The newest line, 8.0, was released July 28, 2025. The next scheduled end of life is 7.2 on June 16, 2027 — 233 days from this build. The longest-supported line currently published is 8.0, to January 28, 2030.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
FortiWeb security intelligence
CISA KEV history: FortiWeb is named in CISA's Known Exploited Vulnerabilities catalog 5 times, most recently on 2026-01-27. Derived from CISA's live catalog at every build.
What does FortiWeb end of life mean for your organization?
When a version of FortiWeb 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 FortiWeb 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 FortiWeb 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, check whether the vendor or a third party sells extended support with security patches for your FortiWeb version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
FortiWeb has 24 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 FortiWeb 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."