FortiSandbox 3.2 · Version Status
FortiSandbox 3.2 End of Life Date
FortiSandbox 3.2 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
FortiSandbox 3.2 is past end of life. This version no longer receives security patches. 679 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 30, 2024
679 days past EOL
Latest Release
3.2
Standard release
Release Date
Apr 30, 2020
FortiSandbox 3.2 series
Lifecycle detail
FortiSandbox 3.2 was released on April 30, 2020 and support ended on October 30, 2024 — a supported lifespan of 4 years and 6 months, in line with the 4 years and 6 months median for FortiSandbox releases. It has been without security patches for 1 year and 10 months. 2 newer FortiSandbox releases have shipped since.
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 →
Extended Support
Extended FortiSandbox 3.2 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All FortiSandbox Versions
| Version | Latest | EOL Date | Status |
|---|
| 1.2 |
1.2 |
Aug 3, 2018 |
EOL |
| 1.3 |
1.3 |
Dec 25, 2018 |
EOL |
| 1.4 |
1.4 |
Feb 11, 2019 |
EOL |
| 2.0 |
2.0 |
Jul 6, 2019 |
EOL |
| 2.1 |
2.1 |
Jan 13, 2020 |
EOL |
| 2.2 |
2.2 |
Sep 15, 2020 |
EOL |
| 2.3 |
2.3 |
Feb 28, 2021 |
EOL |
| 2.4 |
2.4 |
Nov 3, 2021 |
EOL |
What does FortiSandbox 3.2 end of life mean?
When FortiSandbox 3.2 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running FortiSandbox 3.2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to FortiSandbox 5.2 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does FortiSandbox 3.2 reach end of life?
FortiSandbox 3.2 reached end of life on October 30, 2024. This version is no longer receiving security patches.
Is FortiSandbox 3.2 still supported?
No. FortiSandbox 3.2 reached end of life on October 30, 2024 and is no longer receiving security patches.
What should I upgrade to from FortiSandbox 3.2?
The recommended upgrade from FortiSandbox 3.2 is
FortiSandbox 5.2 — the latest actively supported version. Check the
FortiSandbox full timeline for all supported versions.
What are the security risks of running FortiSandbox 3.2 past EOL?
When FortiSandbox 3.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL FortiSandbox should migrate immediately or implement compensating controls.