CVE-2026-121529: Fortinet2Shell
- Vendor
- Fortinet
Fortinet2Shell is an origin-validation vulnerability in the local API endpoint of Fortinet FortiClient for Windows and macOS, including FortiClient Windows PAM. Improper origin validation, associated with a CORS misconfiguration, permits an attacker-controlled webpage to send requests to a local FortiClient service and cause execution of unauthorized code or commands. Exploitation requires victim interaction, such as visiting a malicious website, but does not require attacker authentication. Affected releases include FortiClient Mac 7.4.0–7.4.7, FortiClient Windows 7.4.0–7.4.7 and 7.2.0–7.2.14, and FortiClient Windows PAM 7.4.7 and 7.2.14.
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 enables unauthorized code or command execution on the affected endpoint and can result in privilege escalation. Depending on the execution privileges obtained, an attacker could install malware, access or modify sensitive information, disrupt endpoint operation, or use the compromised endpoint to access other network systems. The exact execution security context is not specified.
Mitigation
If you can’t patch tonight, do this now.
No vendor workaround or virtual patch is available. Pending updates, reduce exposure to untrusted webpages through web filtering and user warnings, limit unnecessary administrative privileges, and strengthen endpoint monitoring. Review unexpected processes or commands originating from FortiClient, unusual local API activity, privilege changes, and anomalous outbound connections. These measures reduce risk or support detection but do not remediate the vulnerability.
Remediation
Patch, then assume compromise.
Upgrade affected FortiClient Mac 7.4 installations to 7.4.8 or later. Upgrade affected FortiClient Windows and FortiClient Windows PAM 7.4 installations to 7.4.8 or later, and affected 7.2 installations to 7.2.15 or later. The 8.0 branches and FortiClient Mac 7.2 are listed as unaffected. Prioritize privileged-user endpoints and Windows PAM installations, and verify installed versions after deployment.
Exploits
4 exploits validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit.
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.
Frequently asked questions
- Is CVE-2026-121529 exploited in the wild?
- As of Nov 16, 2026, Mallory has no reports of CVE-2026-121529 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-121529?
- Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2026-121529, the earliest disclosed Nov 11, 2026.
- Is there a patch for CVE-2026-121529?
- Upgrade affected FortiClient Mac 7.4 installations to 7.4.8 or later. Upgrade affected FortiClient Windows and FortiClient Windows PAM 7.4 installations to 7.4.8 or later, and affected 7.2 installations to 7.2.15 or later.
- What products are affected by CVE-2026-121529?
- Fortinet Forticlientmac, Fortinet Forticlientwindows, and Fortinet Forticlientwindowspam.
- How severe is CVE-2026-121529?
- CVE-2026-121529 has a CVSS v3.1 score of 9.6 (Critical) and an EPSS score of 0.22% (12th percentile) as of Nov 16, 2026.
Recent activity
26 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.