FortiProxy End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all FortiProxy versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0 | Apr 11, 2018 | Oct 11, 2022 | 1422 days past EOL | EOL |
| 1.1 | 1.1 | Dec 22, 2018 | Jun 22, 2023 | 1168 days past EOL | EOL |
| 1.2 | 1.2 | Jan 30, 2019 | Jul 30, 2023 | 1130 days past EOL | EOL |
| 2.0 | 2.0 | Nov 15, 2020 | May 15, 2025 | 475 days past EOL | EOL |
| 7.0 | 7.0 | Aug 24, 2021 | Feb 24, 2026 | 190 days past EOL | EOL |
| 7.2 | 7.2 | Sep 20, 2022 | Mar 20, 2027 | 199 days remaining | Active |
| 7.4 | 7.4 | Jul 24, 2023 | Jan 24, 2028 | 509 days remaining | Active |
| 7.6 | 7.6 | Sep 30, 2024 | Mar 30, 2029 | 940 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/fortiproxy)
FortiProxy lifecycle status — the real story
FortiProxy secure web gateway lifecycle from Fortinet's public product life cycle portal (same verified endpoint and mapping as FortiManager: support = End of Engineering Support, eol = End of Support; fetched 2026-09-02). All 8 published lines included (1.0 through 7.6).
KEV context: CISA files five exploited CVEs against joint strings 'FortiOS and FortiProxy' (CVE-2024-55591 and CVE-2025-24472 — the January 2025 authentication-bypass wave — plus CVE-2023-27997 'FortiOS and FortiProxy SSL-VPN', CVE-2018-13382, CVE-2018-13383). The 7.0 line passed End of Support 2026-02-24 with two of those KEV CVEs disclosed while it was still in 'Must Fix' scope; 2.0 passed End of Support 2025-05-15.
The KEV force override is scoped to FortiProxy only through the joint product strings; FortiOS itself is tracked as a separate upstream product.
FortiProxy release and support pattern
Across the 8 release lines with a published release date, FortiProxy 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 8 release lines tracked, 5 are past end of life and 3 are still within support. The newest line, 7.6, was released September 30, 2024. The next scheduled end of life is 7.2 on March 20, 2027 — 199 days from this build. The longest-supported line currently published is 7.6, to March 30, 2029.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
FortiProxy security intelligence
CISA KEV history: FortiProxy is named in CISA's Known Exploited Vulnerabilities catalog 5 times, most recently on 2025-03-18, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does FortiProxy end of life mean for your organization?
When a version of FortiProxy 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 FortiProxy 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 FortiProxy 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 FortiProxy versions. This is a bridge, not a permanent solution — plan your migration in parallel.
FortiProxy has 5 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 FortiProxy 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."