Exploited CVEs / Fortinet / CVE-2026-35616
CVE-2026-35616
Fortinet FortiClient EMS Improper Access Control Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-04-09 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Fortinet PSIRT Advisories, linked below.
Actively exploited Fortinet FortiClient EMS vulnerability, Critical severity, CVSS 9.8. Added to the CISA KEV catalog 2026-04-06.
Risk summary
Updated July 26, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva AI Opinion for CVE-2026-35616
The second actively exploited FortiClient EMS flaw of spring 2026, this improper access control bug lets an unauthenticated attacker execute code or commands via crafted requests, rated Critical at CVSS 9.8 with an 89% EPSS score. CISA confirmed exploitation on 2026-04-06, a week before the companion SQL injection. Two in-the-wild Critical flaws in one endpoint management product in one month argues for getting it off the internet entirely.
Do this: Apply both April EMS fixes together and restrict the EMS server to VPN or internal access only.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-35616
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2026-35616
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
CISA required action
Federal (BOD 22-01) remediation due date: 2026-04-09 (past due).
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Official fix for CVE-2026-35616
The authoritative fix and affected-version list are published by the vendor. Find the FortiClient EMS advisory on Fortinet PSIRT Advisories.
Common questions about CVE-2026-35616
Is CVE-2026-35616 actively exploited?
Yes. CVE-2026-35616 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-04-06, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 89%.
What is the CISA deadline and required action for CVE-2026-35616?
CISA set the federal (BOD 22-01) remediation due date at 2026-04-09, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
What fixes CVE-2026-35616?
The authoritative fix is in the vendor advisory: see Fortinet PSIRT Advisories for the patched FortiClient EMS versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2026-35616?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-35616's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).
More exploited Fortinet CVEs
The newest Fortinet entries on the CISA KEV catalog:
All Fortinet exploited CVEs on one page: Fortinet vulnerabilities actively exploited.
Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.
