endoflife.ai
FortiClient EMS FortiClient EMS 7.2 FortiClient EMS 7.4 End-of-support edge devices

FortiClient EMS 7.2 End of Support: August 1, 2027

By Scott Bissett  ·  Published: November 21, 2026  ·  Reference guide  ·  Dates from Fortinet's product life cycle data, read on the day of publication. The End of Support dates of the supported lines are re-checked against Fortinet daily.

FortiClient EMS 7.2 reaches End of Support on August 1, 2027, and FortiClient EMS 7.4 reaches End of Support on December 3, 2028. Those are the End of Support Dates (EOS) Fortinet lists for the two lines. Each line has an earlier milestone, the End of Engineering Support Date (EOES). For EMS 7.2 it has passed: it was February 1, 2026, so 7.2 is now in the phase that Fortinet's Product Life Cycle page calls "Must Fix" support. EMS 7.4 is in engineering support until June 3, 2027. The lifecycle dates on this page are from Fortinet's Product Life Cycle data, which we read directly.

Why the management server's dates deserve attention. FortiClient EMS is the server that manages the FortiClient installations on an organization's endpoints. CISA's Known Exploited Vulnerabilities catalog lists 3 FortiClient EMS vulnerabilities, and CISA marks 1 of them as known to be used in ransomware campaigns. Fortinet's advisories give the fix for each affected line as a newer patch release of that line, so the line a server runs and the patch it is on both matter. The table below has all three.
Quick answer: The FortiClient EMS 7.2 end-of-life (EOL) date is August 1, 2027. Active support ended on February 1, 2026. Every FortiClient EMS version's release and end-of-support date is on the FortiClient EMS lifecycle page. Running a FortiClient EMS version that is past end of life? See the support options on this page ↓

Key Dates at a Glance

Running FortiClient EMS past end of life?
Extended support past the official EOL date exists for many products in this position — whether it covers FortiClient EMS 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.” Free, no obligation.

Free · No obligation · Independent — we track the dates, vendors don’t pay for placement · dates verified against vendor sources. See all support options →

FortiClient EMS lines and their dates

EMS lineRelease Date (GA)End of Engineering Support Date (EOES)End of Support Date (EOS)
FortiClient EMS 8.0July 2, 2026July 2, 2029January 2, 2031
FortiClient EMS 7.4June 3, 2024June 3, 2027December 3, 2028
FortiClient EMS 7.2February 1, 2023February 1, 2026August 1, 2027
FortiClient EMS 7.0April 27, 2021April 27, 2024October 27, 2025
FortiClient EMS 6.4May 12, 2020May 12, 2023November 12, 2024

Column names are Fortinet's own, from the Software tab of its Product Life Cycle page, where the product is listed as FortiClient Enterprise Management Server (EMS). Every line older than 7.2 is past its End of Support date; all of them are on our FortiClient EMS page. Fortinet lists the FortiClient endpoint software for Windows, Mac and Linux as separate entries with their own dates; this guide covers the EMS server.

What Fortinet's two dates mean

Fortinet prints its Software Support Policy above the tables on its Product Life Cycle page. It applies to firmware for appliances and to applications installed on customer systems, which is what EMS is. This is what it says, in order.

The page does not list what qualifies as a Must Fix. The fuller definitions are in the Fortinet Product Life Cycle Policy document that the page links to. Fortinet's dates for EMS 6.4 through 8.0 match the policy's arithmetic to the day: EOES is thirty-six months after release and EOS is eighteen months after EOES.

FortiClient EMS in CISA's Known Exploited Vulnerabilities catalog

CISA's catalog lists 3 FortiClient EMS vulnerabilities. The affected versions and solutions below are copied from the Fortinet advisory for each one.

CVEFortinet advisoryAdded to CISA KEVAffected EMS versions in the advisorySolution in the advisory
CVE-2023-48788FG-IR-24-007March 25, 20247.2.0 through 7.2.2; 7.0.1 through 7.0.10. EMS 6.4: not affectedUpgrade to 7.2.3 or above; upgrade to 7.0.11 or above
CVE-2026-35616FG-IR-26-099April 6, 20267.4.5 through 7.4.6. EMS 7.2 and 8.0: not affectedUpgrade to 7.4.7 or above
CVE-2026-21643FG-IR-25-1142April 13, 20267.4.4. EMS 7.2 and 8.0: not affectedUpgrade to 7.4.5 or above

Two things in this table matter for planning.

CVE-2023-48788 is the entry CISA marks as known to be used in ransomware campaigns. Read the advisory itself before acting on any row: Fortinet revises advisories, and each one carries its own notes.

Moving off EMS 7.2: what Fortinet's release notes say

The move from 7.2 is a change of platform, not only a change of version. These points are from the FortiClient EMS 7.2.15, 7.4.8 and 8.0.1 release notes on Fortinet's documentation site.

The lines above 7.2

What a FortiClient EMS owner should plan

  1. On EMS 7.0 or older: the line is past End of Support. EMS 7.0 passed its EOS date on October 27, 2025. Move to a line that is still inside a support phase.
  2. On EMS 7.2: get to the newest 7.2 patch release first. Fortinet's policy ties support to the latest patch release of each version. Fortinet's FortiClient 7.2 documentation lists the EMS release notes for each one.
  3. Plan the move to 7.4 as a server migration. It needs a Linux server from the list in the release notes and a license type the target release accepts. Fortinet's EMS migration tool is the route its release notes describe. Because there is no downgrade, keep the 7.2 server intact until the 7.4 server is confirmed.
  4. Land on a current 7.4 patch. Fortinet's advisories for both 2026 entries in CISA's catalog give a later 7.4 patch release as the solution. Check the two advisories in the table above against the release you install.
  5. Treat 8.0 as the step after 7.4. Fortinet's release notes route 7.2 through 7.4. Endpoints need FortiClient 7.4 or later before the server moves to 8.0.
  6. On EMS 7.4: engineering support runs to June 3, 2027. Put both 7.4 dates in the asset register, and stay on the newest 7.4 patch.

The EOL Checker looks up one product and version. The end-of-support edge device list covers the Fortinet devices at the network edge.

Frequently Asked Questions

When does FortiClient EMS 7.2 reach end of support?

FortiClient EMS 7.2 reaches End of Support on August 1, 2027. Its End of Engineering Support date was February 1, 2026. Both dates are from Fortinet's product life cycle data.

When does FortiClient EMS 7.4 reach end of support?

FortiClient EMS 7.4 reaches End of Engineering Support on June 3, 2027 and End of Support on December 3, 2028.

Is FortiClient EMS 7.0 still supported?

No. FortiClient EMS 7.0 passed its End of Support date on October 27, 2025. Its End of Engineering Support date was April 27, 2024.

Can FortiClient EMS 7.2 be upgraded straight to 8.0?

No, by Fortinet's FortiClient EMS 8.0.1 release notes. They say 8.0 does not support direct migration from 7.2, and that EMS 7.2 users must first migrate to a supported 7.4 version.

Does FortiClient EMS 7.4 run on Windows Server?

No. Fortinet's release notes describe EMS 7.2 as Windows Server-based and EMS 7.4 as Linux-based. The FortiClient EMS 7.4.8 release notes list Ubuntu 22.04 and 24.04, Red Hat Enterprise Linux 9 and CentOS Stream 9 as server operating systems. Fortinet provides an EMS migration tool for the move from 7.2 to 7.4.

Which FortiClient EMS vulnerabilities are in CISA's Known Exploited Vulnerabilities catalog?

CISA's catalog lists 3 FortiClient EMS vulnerabilities: CVE-2023-48788, added on March 25, 2024; CVE-2026-35616, added on April 6, 2026; and CVE-2026-21643, added on April 13, 2026. Fortinet's advisories give the affected versions and the fixed release for each.

Which FortiClient EMS version has the longest support left?

FortiClient EMS 8.0. Its End of Engineering Support date is July 2, 2029 and its End of Support date is January 2, 2031.

What is the difference between EOES and EOS for FortiClient EMS?

End of Engineering Support (EOES) closes the engineering support period, which Fortinet's Product Life Cycle page sets at thirty-six months from the GA release date. End of Support (EOS) comes eighteen months later, at the end of the phase the page calls Must Fix support. After EOS, the page says Fortinet is under no obligation to provide support services.

Related

© 2026 endoflife.ai · How we verify our dates · API · About