CVE-2026-35616 Elastic Security · Elastic

Detect CVE-2026-35616 — Fortinet FortiClient EMS Improper Access Control Exploitation in Elastic Security

Detects exploitation attempts targeting CVE-2026-35616, an improper access control vulnerability (CWE-284) in Fortinet FortiClient Enterprise Management Server (EMS). This vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog, indicating active exploitation in the wild. Attackers may leverage this flaw to bypass access controls on the EMS server, potentially enabling unauthorized configuration changes, endpoint agent manipulation, or lateral movement through managed endpoints.

MITRE ATT&CK

Tactic
Initial Access Persistence Privilege Escalation Lateral Movement

Elastic Detection Query

Elastic Security (Elastic)
eql
sequence by host.name with maxspan=10m
  [network where process.name : ("fcems*", "FortiEMS*", "fcemsvc*") and
   (network.direction == "ingress" or network.direction == "inbound") and
   destination.port in (8013, 8014, 443, 10443)]
  [any where
   (event.outcome == "failure" or event.action in ("access-denied", "authorization-failure", "privilege-escalation")) and
   (process.name : ("fcems*", "FortiEMS*") or host.name : ("*ems*", "*forticlient*"))
  ]
critical severity medium confidence

EQL sequence rule correlating inbound network connections to known FortiClient EMS service ports with subsequent access control failure events on the same host within a 10-minute window. Designed for environments shipping Fortinet process and network telemetry to Elastic.

Data Sources

Elastic EndpointFortinet integration logsNetwork packet metadata

Required Tables

logs-*metrics-*traces-*

False Positives & Tuning

  • Legitimate remote EMS administration sessions from authorised management stations
  • FortiClient agent heartbeat connections to EMS that coincide with policy push failures
  • High-frequency endpoint check-ins during large-scale rollouts causing benign access denials
  • Monitoring tools polling EMS API on standard ports triggering sequence matches

Other platforms for CVE-2026-35616


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1FortiClient EMS Unauthenticated API Endpoint Probe

    Expected signal: Web server access log entries on EMS showing HTTP requests to API paths from an unknown source IP, with response codes logged. Network flow records show connections from test host to EMS port 8013.

  2. Test 2FortiClient EMS Privilege Escalation via Access Control Bypass (Simulated)

    Expected signal: EMS audit log entries recording the low-privilege user's access attempts to admin-tier endpoints. Windows Security Event Log 4648 if token acquisition involved explicit credential use.

  3. Test 3FortiClient EMS Management Port Reconnaissance from External Network Segment

    Expected signal: Network IDS/IPS alerts for port scan activity targeting EMS management ports. Firewall deny logs if EMS ports are restricted. NetFlow records showing probe connections from test segment to EMS IP.

  4. Test 4FortiClient Agent Mass Policy Modification via Compromised EMS

    Expected signal: EMS audit log entry recording policy creation event with the admin token's associated username. API access log entry for POST to /api/v1/policies. Managed endpoint logs showing receipt of new policy push if EMS propagates it.

Unlock Pro Content

Get the full detection package for CVE-2026-35616 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections