Threats / Fortinet / CVE-2026-35616
CVE-2026-35616
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Fortinet FortiClient EMS vulnerability
Fortinet FortiClient EMS contains an improper access control vulnerability allowing unauthenticated attackers to execute unauthorized code or commands via crafted requests.
Verdict
Today item — known-exploited.
An unauthenticated remote attacker can exploit improper access controls in FortiClient EMS to execute arbitrary code or commands, potentially compromising endpoint management infrastructure and connected systems.
CISA KEV Yes · 2026-04-065EPSS 0.8894 (verify live)6Exploit Weaponized · public PoC7CVSS 9.13CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
10 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-04-06).
Probability (EPSS)
EPSS 0.8894 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C) · Affected: Fortinet, FortiClient EMS. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-284 Improper Access Control — weakness family: Authorization / access control.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 2 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request targeting the unauthenticated endpoint in FortiClient EMS.
Business
The organization's endpoint management system is exposed to unauthorized access without authentication barriers.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I bypass access controls and execute arbitrary code on the EMS server.
Business
Attackers gain control of the centralized management platform that oversees all client endpoints.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage EMS compromise to deploy malware or commands across the managed endpoint fleet.
Business
The organization faces widespread endpoint compromise, data exfiltration, and operational disruption across its infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05