FortiProxy 2.0 · Version Status

FortiProxy 2.0 End of Life Date

FortiProxy 2.0 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

FortiProxy 2.0 is past end of life. This version no longer receives security patches. 475 days past EOL — migrate to a supported version immediately.
EOL Date
May 15, 2025
475 days past EOL
Latest Release
2.0
Standard release
Release Date
Nov 15, 2020
FortiProxy 2.0 series
Lifecycle detail

FortiProxy 2.0 was released on November 15, 2020 and support ended on May 15, 2025 — a supported lifespan of 4 years and 6 months, in line with the 4 years and 6 months median for FortiProxy releases. It has been without security patches for 1 year and 4 months.

← FortiProxy 1.2 All FortiProxy versions FortiProxy 7.0 →
65 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
35/40
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 →
Recommended upgrade path
FortiProxy 7.6
Latest release: 7.6 · EOL: Mar 30, 2029
View full FortiProxy timeline →
Extended Support
Extended FortiProxy 2.0 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All FortiProxy Versions
VersionLatestEOL DateStatus
1.0 1.0 Oct 11, 2022 EOL
1.1 1.1 Jun 22, 2023 EOL
1.2 1.2 Jul 30, 2023 EOL
2.0 2.0 May 15, 2025 EOL
7.0 7.0 Feb 24, 2026 EOL
7.2 7.2 Mar 20, 2027 Active
7.4 7.4 Jan 24, 2028 Active
7.6 7.6 Mar 30, 2029 Active

What does FortiProxy 2.0 end of life mean?

When FortiProxy 2.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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running FortiProxy 2.0 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to FortiProxy 7.6 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does FortiProxy 2.0 reach end of life?
FortiProxy 2.0 reached end of life on May 15, 2025. This version is no longer receiving security patches.
Is FortiProxy 2.0 still supported?
No. FortiProxy 2.0 reached end of life on May 15, 2025 and is no longer receiving security patches.
What should I upgrade to from FortiProxy 2.0?
The recommended upgrade from FortiProxy 2.0 is FortiProxy 7.6 — the latest actively supported version. Check the FortiProxy full timeline for all supported versions.
What are the security risks of running FortiProxy 2.0 past EOL?
When FortiProxy 2.0 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 FortiProxy should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →