FortiMail End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all FortiMail versions. Dates read at the vendor's own lifecycle pages (support.fortinet.com). Updated at every deploy.
FortiMail 8.0 is supported until November 6, 2030, its end-of-support date. Active support for FortiMail 8.0 ends on May 6, 2029. The next FortiMail version to reach end of life is 7.2, on November 10, 2026. 20 of 24 tracked FortiMail versions are past end of life; the most recent to reach it, 7.0, did so on November 17, 2025. The full FortiMail 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.8 | 2.8 | Jan 15, 2007 | Jan 15, 2010 | 6119 days past EOL | EOL |
| 3.0 | 3.0 | Aug 3, 2007 | Aug 3, 2010 | 5919 days past EOL | EOL |
| 3.1 | 3.1 | Nov 1, 2007 | Nov 1, 2010 | 5829 days past EOL | EOL |
| 3.2 | 3.2 | Dec 24, 2007 | Dec 24, 2010 | 5776 days past EOL | EOL |
| 3.3 | 3.3 | Apr 18, 2008 | Apr 18, 2011 | 5661 days past EOL | EOL |
| 3.4 | 3.4 | Aug 1, 2008 | Aug 1, 2011 | 5556 days past EOL | EOL |
| 3.5 | 3.5 | May 7, 2009 | May 7, 2012 | 5276 days past EOL | EOL |
| 4.0 | 4.0 | Nov 24, 2009 | Nov 24, 2012 | 5075 days past EOL | EOL |
| 4.1 | 4.1 | Jul 12, 2010 | Jul 12, 2013 | 4845 days past EOL | EOL |
| 4.2 | 4.2 | Mar 11, 2011 | Mar 11, 2014 | 4603 days past EOL | EOL |
| 4.3 | 4.3 | Feb 7, 2012 | Aug 7, 2016 | 3723 days past EOL | EOL |
| 5.0 | 5.0 | Feb 28, 2013 | Aug 28, 2017 | 3337 days past EOL | EOL |
| 5.1 | 5.1 | Dec 19, 2013 | Jun 19, 2018 | 3042 days past EOL | EOL |
| 5.2 | 5.2 | Aug 25, 2014 | Feb 25, 2019 | 2791 days past EOL | EOL |
| 5.3 | 5.3 | Nov 30, 2015 | May 30, 2020 | 2331 days past EOL | EOL |
| 5.4 | 5.4 | Jul 25, 2017 | Jan 25, 2022 | 1726 days past EOL | EOL |
| 6.0 | 6.0 | May 29, 2018 | Nov 29, 2022 | 1418 days past EOL | EOL |
| 6.2 | 6.2 | Aug 9, 2019 | Feb 9, 2024 | 981 days past EOL | EOL |
| 6.4 | 6.4 | May 8, 2020 | Nov 8, 2024 | 708 days past EOL | EOL |
| 7.0 | 7.0 | May 17, 2021 | Nov 17, 2025 | 334 days past EOL | EOL |
| 7.2 | 7.2 | May 10, 2022 | Nov 10, 2026 | 24 days remaining | Warning |
| 7.4 | 7.4 | Jul 4, 2023 | Jan 4, 2028 | 444 days remaining | Active |
| 7.6 | 7.6 | Aug 1, 2024 | Feb 1, 2029 | 838 days remaining | Active |
| 8.0 | 8.0 | May 6, 2026 | Nov 6, 2030 | 1481 days remaining | Active |
[](https://endoflife.ai/fortimail)
FortiMail lifecycle status — the real story
FortiMail email security gateway 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 24 published software lines included (2.8 through 8.0); hardware appliance rows on the same endpoint are skipped, they belong to a hardware platform file. 20 of the 24 lines are past End of Support as of the fetch date.
KEV context (CISA catalog 2026.10.08): two entries. CVE-2026-104286 (path traversal, added 2026-10-01) is filed under 'Fortinet / FortiMail' and matches by name; CVE-2025-32756 (stack-based overflow in the API, added 2025-05-14) is filed under 'Fortinet / Multiple Products', and Fortinet advisory FG-IR-25-254 lists FortiMail 7.0 through 7.6 as affected, so it is joined by a force override. No version scoping is asserted beyond the advisories.
FortiMail release and support pattern
Across the 24 release lines with a published release date, FortiMail has shipped a new line roughly every 10 months (median interval). A line typically stays supported for about 4.5 years from its release to its end-of-life date.
Of the 24 release lines tracked, 20 are past end of life and 4 are still within support. The newest line, 8.0, was released May 6, 2026. The next scheduled end of life is 7.2 on November 10, 2026 — 23 days from this build. The longest-supported line currently published is 8.0, to November 6, 2030.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
FortiMail security intelligence
CISA KEV history: FortiMail is named in CISA's Known Exploited Vulnerabilities catalog 2 times, most recently on 2026-10-01. Derived from CISA's live catalog at every build.
What does FortiMail end of life mean for your organization?
When a version of FortiMail 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 FortiMail 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 FortiMail 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 FortiMail versions. This is a bridge, not a permanent solution — plan your migration in parallel.
FortiMail has 20 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 FortiMail 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."