Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-35616: Authentication Bypass and Remote Code Execution in Fortinet FortiClient EMS

Published Apr 4, 2026 · Updated 7 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS9.8Critical · v3.1
EPSS94.0%100th percentile
CISA KEVYesAdded Apr 6, 2026
In the wildActivePer CISA KEV
Vendor
Fortinet
IdentifiersCVE-2026-35616CWE-284 · Improper Access Control

CVE-2026-35616 is an improper access control vulnerability affecting Fortinet FortiClient Endpoint Management Server (EMS) versions 7.4.5 and 7.4.6. Insufficient authentication and authorization enforcement in the EMS API allows remote, unauthenticated attackers to access protected functionality through crafted requests and execute unauthorized code or commands. Fortinet has confirmed exploitation in the wild. The FortiClient EMS 7.2 branch is unaffected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise the EMS server and its centralized endpoint-administration capabilities, enabling unauthorized administrative access, code or command execution, and modification of security policies and managed-device configurations. Operator records describe persistence through unauthorized administrator accounts and endpoint payload distribution through modified VPN connection scripts, although those campaign-specific claims were not independently verified. Compromise can facilitate further endpoint intrusion, data theft, and operational disruption.

Mitigation

If you can’t patch tonight, do this now.

Restrict EMS management and API access to trusted administrative networks and remove direct public exposure. Monitor for suspicious API requests, unauthorized administrators, and modified VPN connection scripts. These measures reduce exposure and support detection but do not replace the vendor hotfix or upgrade; Fortinet specifies no separate workaround.

Remediation

Patch, then assume compromise.

Apply the Fortinet hotfix corresponding to FortiClient EMS 7.4.5 or 7.4.6 using the relevant release-note instructions, or upgrade to FortiClient EMS 7.4.7 or later. Verify the installed version and hotfix status after remediation. Fortinet states that the hotfix entirely prevents exploitation. FortiClient Cloud and FortiSASE have already been remediated and require no customer action. For potentially compromised deployments, investigate unauthorized administrator accounts, altered VPN connection scripts, unusual API activity, and unexpected configuration changes; remove unauthorized access and rotate compromised credentials.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 9 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-35616This repository is a small standalone Python PoC for CVE-2026-35616 affecting Fortinet FortiClient EMS. It contains only two files: a README with usage/affected-version notes and one executable script, cve_2026_35616.py, which is the clear entry point. The script is not part of a larger exploit framework. The exploit targets a pre-authentication bypass in certificate-based authentication logic. Its core technique is to generate a self-signed X.509 certificate on the fly, URL-encode it, and send it in the X-SSL-CLIENT-CERT header while forcing X-SSL-CLIENT-VERIFY: SUCCESS. The script assumes the server-side component trusts these headers directly instead of validating the certificate cryptographically. Operational flow: (1) build the HTTPS base URL from target and port; (2) discover likely acceptable certificate common names (CNs) by invoking openssl s_client to inspect acceptable client CA names, by downloading certificates from /api/v1/ztna_certificates/download and parsing their CNs, and by reading a Serial Number response header from the target root page; (3) if discovery fails, fall back to hardcoded CN guesses (support, fortinet-ca2); (4) iterate through candidate CNs and attempt the bypass against /api/v1/system/capabilities; (5) once a working CN is found, probe several protected API endpoints with GET/POST/PATCH requests; and (6) print equivalent curl commands for manual reuse. Main exploit capabilities include unauthorized retrieval of system capabilities, version information, and public address settings, plus interaction with FortiGate-related API endpoints. The script is more than a detector because it actively performs the bypass and accesses protected resources, but it does not deploy a post-exploitation shell or arbitrary command payload. As written, it is an operational PoC for unauthorized API access against vulnerable FortiClient EMS instances.Alaatk · Disclosed Apr 19, 2026 · python · markdown · network · webOperationalCVE-2026-35616This repository is a small standalone Python exploit for CVE-2026-35616 targeting a Fortinet API certificate-chain verification bypass. The repo contains three files: a README with usage guidance, one executable exploit script (exploit.py), and a requirements file. The exploit is not framework-based. Core capability: the script attempts to bypass client-certificate based access controls on Fortinet API endpoints by discovering acceptable CA/Common Names, generating a forged self-signed X.509 certificate with a candidate CN, and sending requests that spoof upstream TLS-authentication headers. It uses the headers X-SSL-CLIENT-VERIFY: SUCCESS and X-SSL-CLIENT-CERT containing a URL-encoded PEM certificate. If the target trusts these headers improperly, the script can access protected API routes. Operational flow: it builds a target base URL from command-line arguments (default 172.16.50.51:443), optionally enumerates acceptable client certificate CA names via openssl s_client, tests candidate CNs against /api/v1/system/capabilities, selects a working CN when HTTP/retval indicate success, then probes several additional API endpoints. It stores results in a JSON file under results/ and prints equivalent curl commands for manual verification. Notable targeted endpoints include /api/v1/system/capabilities, /api/v1/system/version, /api/v1/settings/server/public_address, /api/v1/fabric_device_auth/fortigate/init, and /api/v1/fortigate/info. The exploit is operational rather than a simple detector because it actively forges a certificate, performs authenticated bypass attempts, and retrieves protected API data. The payload is basic and hardcoded around header/certificate spoofing rather than a customizable post-exploitation framework.wa6n3r · Disclosed Apr 20, 2026 · python · markdown · network · webOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FortinetForticlient Emsapplication
FAQ

Frequently asked questions

Is CVE-2026-35616 exploited in the wild?
Yes. As of Nov 15, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Apr 6, 2026.
Is there a public exploit for CVE-2026-35616?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2026-35616, the earliest disclosed Apr 19, 2026.
Is there a patch for CVE-2026-35616?
Apply the Fortinet hotfix corresponding to FortiClient EMS 7.4.5 or 7.4.6 using the relevant release-note instructions, or upgrade to FortiClient EMS 7.4.7 or later. Verify the installed version and hotfix status after remediation.
What products are affected by CVE-2026-35616?
Fortinet Forticlient Ems.
How severe is CVE-2026-35616?
CVE-2026-35616 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 94.0% (100th percentile) as of Nov 15, 2026.
Activity feed

Recent activity

352 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
cysecurity newsNews · Oct 26, 2026Ransomware Affiliates Built an AI-Powered Attack Platform That Logged Its Own Crimes - CySecurity News - Latest Information Security and Hacking IncidentsAn authentication bypass vulnerability in FortiClient EMS exploited by the ransomware-affiliate operation to create backdoor administrator accounts across more than 4,000 managed endpoints.Read more ↗the hacker newsNews · Oct 23, 2026Exposed Infrastructure Reveals How Ransomware Affiliates Used AI Agents to Execute IntrusionsAn authentication bypass vulnerability affecting Fortinet FortiClient, described in the campaign context as targeting FortiClient EMS gateways. Operators actively exploited it for initial access in ransomware-linked intrusions.Read more ↗hackreadNews · Oct 21, 2026INC and The Gentlemen Ransomware Affiliates Expose 8,257 AI MessagesA FortiClient EMS vulnerability reportedly targeted by ransomware affiliates. Their records claimed 2,236 targets, 108 newly created administrator accounts, and 4,140 managed endpoints. These figures were not independently verified, and the content does not describe the underlying technical flaw.Read more ↗cryptika blogNews · Oct 21, 2026Hackers Use Claude AI to Plan Ransomware Attacks, Then Accidentally Expose Their Secrets | Cryptika CybersecurityA vulnerability in FortiClient EMS reportedly exploited for initial access by operators involved in the ransomware activity. The claim comes from exposed operator records and was not independently verified by STRU. The content does not describe the technical flaw.Read more ↗
+43 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence12Every report linking this CVE to a named adversary.
Associated malware28Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity153Community discussion across Reddit, Mastodon, and other social sources.