FortiMail 8.0 · Version Status
FortiMail 8.0 End of Life Date
FortiMail 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.
✓
FortiMail 8.0 is actively supported. EOL date: November 6, 2030.
📅 Get reminded before FortiMail 8.0 reaches EOL on November 6, 2030 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
Automating this check?
GET https://api.endoflife.ai/v1/score/fortimail/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 6, 2030
1449 days remaining
Latest Release
8.0
Standard release
Release Date
May 6, 2026
FortiMail 8.0 series
Where these dates come from
End of lifeNov 6, 2030Vendor's own page, checked by a person · support.fortinet.com · checked Oct 26, 2026high · 2 sources agree End of active supportMay 6, 2029Vendor's own page, checked by a person · support.fortinet.com · checked Oct 26, 2026high · 2 sources agree ReleaseMay 6, 2026Vendor's own page, checked by a person · support.fortinet.com · checked Oct 26, 2026high · 2 sources agree
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
FortiMail 8.0 was released on May 6, 2026 and support is scheduled to end on November 6, 2030 — a planned supported lifespan of 4 years and 6 months, in line with the 4 years and 6 months median for FortiMail 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.8 |
2.8 |
Jan 15, 2010 |
EOL |
| 3.0 |
3.0 |
Aug 3, 2010 |
EOL |
| 3.1 |
3.1 |
Nov 1, 2010 |
EOL |
| 3.2 |
3.2 |
Dec 24, 2010 |
EOL |
| 3.3 |
3.3 |
Apr 18, 2011 |
EOL |
| 3.4 |
3.4 |
Aug 1, 2011 |
EOL |
| 3.5 |
3.5 |
May 7, 2012 |
EOL |
| 4.0 |
4.0 |
Nov 24, 2012 |
EOL |
What does FortiMail 8.0 end of life mean?
When FortiMail 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 FortiMail 8.0 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to FortiMail 8.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does FortiMail 8.0 reach end of life?
FortiMail 8.0 reaches end of life on November 6, 2030. That is 1449 days remaining.
Is FortiMail 8.0 still supported?
Yes, FortiMail 8.0 is currently supported. The EOL date is November 6, 2030.
What should I upgrade to from FortiMail 8.0?
The recommended upgrade from FortiMail 8.0 is
FortiMail 8.0 — the latest actively supported version. Check the
FortiMail full timeline for all supported versions.
What are the security risks of running FortiMail 8.0 past EOL?
When FortiMail 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 FortiMail should migrate immediately or implement compensating controls.