# CVE-2026-35616: Fortinet FortiClient EMS Improper Access Control

> Unauthenticated attackers can execute unauthorized code or commands on FortiClientEMS via crafted requests due to improper access control.

- **Severity:** Critical 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`)
- **Exploited in the wild:** Yes, since 6 Apr 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-gvcr-mc93-7p8p

## What is CVE-2026-35616?

CVE-2026-35616 is a critical authentication bypass vulnerability in Fortinet FortiClientEMS, published on 4 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A improper access control vulnerability in Fortinet FortiClientEMS 7.4.5 through 7.4.6 may allow an unauthenticated attacker to execute unauthorized code or commands via crafted requests.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-35616?

It affects 1 product.


Products: Fortinet Forticlientems.

## How do I fix CVE-2026-35616?

No fix has been published for CVE-2026-35616 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 9 Apr 2026.

## Is CVE-2026-35616 being exploited?

Yes. Attackers have exploited CVE-2026-35616 in the wild since at least 6 Apr 2026.

Public exploit code:

- Fortinet FortiClientEMS improper access control (github_poc): https://github.com/Alaatk/CVE-2026-35616
- https://github.com/BishopFox/CVE-2026-35616-check (github_poc): https://github.com/BishopFox/CVE-2026-35616-check
- CVE-2026-35616 (github_poc): https://github.com/0xredash/CVE-2026-35616
- CVE-2026-35616 - FortiClient EMS Pre-Authentication API Bypass (CVSS 9.1, CISA KEV). Python & Nmap NSE detection scripts with full technical breakdown. One forged HTTP header bypasses authentication on FortiClient EMS 7.4.5–7.4.6, granting full admin API access to all managed endpoints. (github_poc): https://github.com/keraattin/CVE-2026-35616
- https://github.com/wa6n3r/CVE-2026-35616 (github_poc): https://github.com/wa6n3r/CVE-2026-35616
- Detector de CVE-2026-35616: identifica servidores FortiClient EMS vulnerables (7.4.5-7.4.6). (github_poc): https://github.com/fevar54/CVE-2026-35616-detector.py

## Other vulnerabilities in Fortinet FortiClientEMS

- [CVE-2026-21643](https://insights.sbomify.com/CVE-2026-21643/): Fortinet FortiClient EMS SQL Injection (critical 9.1, exploited in the wild)
- [CVE-2024-23106](https://insights.sbomify.com/CVE-2024-23106/): Auth bypass in FortiClientEMS (high 7.7)
- [CVE-2025-59922](https://insights.sbomify.com/CVE-2025-59922/): SQL injection in FortiClientEMS (medium 6.8)
- [CVE-2026-59836](https://insights.sbomify.com/CVE-2026-59836/): Security feature bypass in FortiClientEMS (medium 6.7)
- [CVE-2026-39809](https://insights.sbomify.com/CVE-2026-39809/): SQL injection in FortiClientEMS (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35616 and fix it if it is affected.

What it is: CVE-2026-35616 is a critical authentication bypass vulnerability in Fortinet FortiClientEMS, published on 4 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-35616 in the wild since at least 6 Apr 2026.

Affected product: Fortinet FortiClientEMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35616/ (Markdown: https://insights.sbomify.com/CVE-2026-35616/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35616
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35616
- OSV: https://osv.dev/vulnerability/CVE-2026-35616

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35616/
Summaries are generated and may contain mistakes; the official description above is the record.