FortiSandbox End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all FortiSandbox versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
FortiSandbox 5.2 is supported until December 10, 2030, its end-of-support date. Active support for FortiSandbox 5.2 ends on June 10, 2029; security fixes continue until that end-of-life date. The next FortiSandbox version to reach end of life is 4.4, on January 10, 2028. 14 of 17 tracked FortiSandbox versions are past end of life; the most recent to reach it, 4.2, did so on November 14, 2025. The full FortiSandbox 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 |
|---|---|---|---|---|---|
| 1.2 | 1.2 | Feb 3, 2014 | Aug 3, 2018 | 2959 days past EOL | EOL |
| 1.3 | 1.3 | Jun 25, 2014 | Dec 25, 2018 | 2815 days past EOL | EOL |
| 1.4 | 1.4 | Aug 11, 2014 | Feb 11, 2019 | 2767 days past EOL | EOL |
| 2.0 | 2.0 | Jan 6, 2015 | Jul 6, 2019 | 2622 days past EOL | EOL |
| 2.1 | 2.1 | Jul 13, 2015 | Jan 13, 2020 | 2431 days past EOL | EOL |
| 2.2 | 2.2 | Mar 15, 2016 | Sep 15, 2020 | 2185 days past EOL | EOL |
| 2.3 | 2.3 | Aug 30, 2016 | Feb 28, 2021 | 2019 days past EOL | EOL |
| 2.4 | 2.4 | May 3, 2017 | Nov 3, 2021 | 1771 days past EOL | EOL |
| 2.5 | 2.5 | Nov 2, 2017 | May 2, 2022 | 1591 days past EOL | EOL |
| 3.0 | 3.0 | Jul 31, 2018 | Jan 31, 2023 | 1317 days past EOL | EOL |
| 3.1 | 3.1 | Jun 18, 2019 | Dec 18, 2023 | 996 days past EOL | EOL |
| 3.2 | 3.2 | Apr 30, 2020 | Oct 30, 2024 | 679 days past EOL | EOL |
| 4.0 | 4.0 | Apr 19, 2021 | Oct 19, 2025 | 325 days past EOL | EOL |
| 4.2 | 4.2 | Apr 13, 2022 | Nov 14, 2025 | 299 days past EOL | EOL |
| 4.4 | 4.4 | Jul 10, 2023 | Jan 10, 2028 | 488 days remaining | Active |
| 5.0 | 5.0 | Nov 7, 2024 | May 7, 2029 | 971 days remaining | Active |
| 5.2 | 5.2 | Jun 10, 2026 | Dec 10, 2030 | 1553 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/fortisandbox)
FortiSandbox lifecycle status — the real story
FortiSandbox sandbox appliance 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 17 published software lines included (1.2 through 5.2); hardware appliance rows on the same endpoint are skipped, they belong to a hardware platform file. 14 of the 17 lines are past End of Support as of the fetch date.
KEV context (CISA catalog 2026.09.08, matched on the display name): CVE-2026-25089 (FortiSandbox, added 2026-07-16); CVE-2026-39808 (FortiSandbox, added 2026-07-16). No version scoping is asserted here; the affected lines are whatever Fortinet's advisory says, and the score uses the catalog join only.
FortiSandbox release and support pattern
Across the 17 release lines with a published release date, FortiSandbox has shipped a new line roughly every 8 months (median interval). A line typically stays supported for about 4.5 years from its release to its end-of-life date.
Of the 17 release lines tracked, 14 are past end of life and 3 are still within support. The newest line, 5.2, was released June 10, 2026. The next scheduled end of life is 4.4 on January 10, 2028 — 488 days from this build. The longest-supported line currently published is 5.2, to December 10, 2030.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
FortiSandbox security intelligence
CISA KEV history: FortiSandbox is named in CISA's Known Exploited Vulnerabilities catalog 2 times, most recently on 2026-07-16. Derived from CISA's live catalog at every build.
What does FortiSandbox end of life mean for your organization?
When a version of FortiSandbox 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: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL FortiSandbox 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 FortiSandbox 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 FortiSandbox versions. This is a bridge, not a permanent solution — plan your migration in parallel.
FortiSandbox has 14 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 FortiSandbox 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."