FortiClient EMS zero-day CVE-2026-35616 exploited; hotfix out for 7.4.5 and 7.4.6

Fortinet hotfixed CVE-2026-35616, a pre-auth API bypass in FortiClient EMS 7.4.5-7.4.6 exploited as a zero-day. CISA set an April 9 deadline. What to check.

TechLogHub Engineering Team
April 5, 2026
3 min read
0 views

Share Article

New FortiClient EMS flaw exploited in attacks, emergency patch released

Fortinet has released emergency hotfixes for CVE-2026-35616, an unauthenticated API access bypass in FortiClient Enterprise Management Server (EMS) that attackers exploited before a patch existed. EMS is the server that pushes policy and software to every managed FortiClient endpoint, so a compromise there is a path onto the whole fleet. It is the second actively exploited critical EMS flaw within weeks.

What happened

Fortinet published advisory FG-IR-26-099 on 4 April 2026. It describes an improper access control weakness (CWE-284) in FortiClient EMS that "may allow an unauthenticated attacker to execute unauthorized code or commands via crafted requests." Fortinet rates it CVSS 9.8 base (9.1 temporal) and says it has observed exploitation in the wild. Security firm Defused, which reported the bug after seeing it used as a zero-day, describes it as a pre-authentication API access bypass that skips authentication and authorisation controls entirely. Fortinet credits Simo Kohonen of Defused and Nguyen Duc Anh.

CISA added CVE-2026-35616 to its Known Exploited Vulnerabilities catalogue on 6 April and ordered US federal civilian agencies to remediate by 9 April. Shadowserver counted roughly 2,000 FortiClient EMS instances exposed to the internet, mostly in the US and Germany.

The disclosure followed CVE-2026-21643 (FG-IR-25-1142), a CVSS 9.8 SQL injection in FortiClient EMS fixed in February and flagged as exploited shortly before. Indicators reported for that flaw include HTTP 500 errors on /api/v1/init_consts, unusual PostgreSQL errors and unauthorised remote management tools on the server.

Who is affected

  • Affected: FortiClient EMS 7.4.5 and 7.4.6.
  • Not affected: FortiClient EMS 7.2 and 8.0, per Fortinet.
  • Cloud: FortiClient Cloud and FortiSASE were fixed by Fortinet; no customer action needed.
  • Fix: the hotfix for 7.4.5 and 7.4.6, which Fortinet says fully prevents the issue, or FortiClient EMS 7.4.7 or later.
  • Older 7.4 builds may still be exposed to CVE-2026-21643 and should move to a fixed release.

What it means for developers and engineering teams

Endpoint management servers are software distribution systems. Whoever controls EMS can change endpoint policy, push installers or scripts, and harvest information about every managed device, which makes them as sensitive as a CI/CD pipeline or a package registry. Two pre-auth flaws in its HTTP API within weeks underline a familiar pattern: management APIs built for internal use end up reachable from the internet, and authentication is enforced in some routes but not all.

If you build admin APIs, the lesson is to enforce authentication centrally (middleware or gateway, deny by default) rather than per handler, and to keep management interfaces off the public internet entirely. Authentication bypasses in this class usually come from one route, path variant or HTTP method that skips the check. A deny-by-default pattern makes the safe behaviour automatic:

// Express example: every /api route requires auth unless explicitly public
const PUBLIC = new Set(['/api/health']);
app.use('/api', (req, res, next) => {
  if (PUBLIC.has(req.path)) return next();
  return requireAuth(req, res, next);
});

Pair that with tests that enumerate every registered route and assert an unauthenticated request gets a 401 or 403. That kind of test catches the forgotten endpoint before an attacker does.

If you operate EMS or similar tools, treat them as tier-zero assets: restricted network access, dedicated admin accounts and full logging. Two critical, pre-auth, exploited bugs in one product within weeks is also a signal to review whether the management plane should be reachable from anywhere other than a hardened admin network.

What to do now

  1. Identify your EMS version in the EMS console (Dashboard or About). If it is 7.4.5 or 7.4.6, apply Fortinet's hotfix immediately or upgrade to 7.4.7 or later.
  2. If you run an earlier 7.4 build, upgrade to a fixed release to close CVE-2026-21643 as well.
  3. Remove internet exposure of the EMS administrative web interface and API. Restrict to a management VLAN or VPN with an allow-list.
  4. Assume compromise if it was exposed: review EMS web and API logs for unauthenticated requests, look for new admin accounts, unexpected deployment packages or policies, and remote management tools you did not install.
  5. Check endpoints for software or scripts pushed via EMS since late March 2026 that do not match change records.
  6. Rotate credentials stored on or used by the EMS server, including AD service accounts and database credentials.

Related on TechLogHub

Sources

Stay Updated

Get the next deep dive in your inbox

Subscribe for product analysis, engineering explainers, and practical guides published on TechLogHub.

See what launched this week

One email a week: new and trending developer tools, fresh comparisons, and what shipped. Unsubscribe in one click.