FortiClient CVE-2026-121529 (Fortinet2Shell) lets websites run code
Fortinet patched critical FortiClient flaw CVE-2026-121529, where a malicious web page can run code; upgrade to 7.4.8 or 7.2.15 or later.
- Published
- Fixed in
- FortiClient Mac 7.4.8, FortiClient Windows 7.4.8, FortiClient Windows PAM 7.4.8, FortiClient Windows 7.2.15, FortiClient Windows PAM 7.2.15 (or later on each branch)
- Exploitation
- No, both outlets report Fortinet says the flaw is not currently known to be exploited, but technical details are public
Live scores
CVE-2026-121529- EPSS
- 0.002
low predicted chance of attack - VEDAS
- 0.053
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
What happened
Fortinet published an advisory on November 10, 2026 for CVE-2026-121529, a critical flaw in FortiClient. Cyber Security News reports a CVSS score of 9.1. GBHackers gives the same score as CVSS v3 and names the advisory FG-IR-26-194. The Fortinet advisory itself was not among the sources we were given, so every detail below is as reported by these two outlets and is not independently confirmed.
Both outlets describe an origin validation error (CWE-346) in a local API endpoint. Researcher Kevin Joensen of Baldur Security reported it and nicknamed it “Fortinet2Shell”. The root cause is a CORS misconfiguration. FortiClient runs a local service on the user’s machine that wrongly trusts requests from web pages (GBHackers). A page controlled by an attacker can send requests to that service and make it run attacker-supplied code (Cyber Security News).
The victim only has to visit the malicious page. Fortinet notes that exploitation needs user interaction. The reported CVSS v3 vector is network attack, low complexity, no privileges required, user interaction required, and changed scope (GBHackers).
The outlets describe the impact slightly differently. Cyber Security News stresses remote code execution and says Joensen confirmed reliable code execution. GBHackers says Fortinet lists the impact as escalation of privilege and that it works reliably on FortiClient with FortiPAM enabled.
Both outlets say Fortinet indicates the flaw is not known to be exploited. Cyber Security News adds that technical details are now public and the attack method is straightforward.
Am I affected?
Affected builds, as listed by both outlets:
- FortiClient Mac 7.4.0 through 7.4.7
- FortiClient Windows 7.4.0 through 7.4.7
- FortiClient Windows PAM 7.4.0 through 7.4.7
- FortiClient Windows 7.2.0 through 7.2.14
- FortiClient Windows PAM 7.2.0 through 7.2.14
Not affected: version 8.0 of these products, and FortiClient Mac 7.2 (Cyber Security News, GBHackers).
Besides the version check, Joensen lists two signs on Windows that may point to a vulnerable install: a service listening on TCP port 9191, and a running FortiVRS.exe process. Cyber Security News notes these signs only suggest exposure and do not show that anyone has attacked the machine (Cyber Security News, GBHackers).
What to do now
- Inventory FortiClient installs and check their versions against the list above.
- Upgrade FortiClient Mac and Windows on the 7.4 branch to 7.4.8 or later, and on the 7.2 branch to 7.2.15 or later. The PAM builds follow the same targets (GBHackers).
- Do not rely on a workaround. Fortinet says no virtual patch exists, so updating is the only fix (Cyber Security News).
- On Windows, search your fleet for a service on TCP port 9191 and for FortiVRS.exe, and patch those systems first (GBHackers).
- Until patching is complete, tell users to avoid untrusted links (GBHackers), and review web filtering rules during deployment (Cyber Security News).
- Read Fortinet’s own advisory (FG-IR-26-194) for the authoritative scope. We did not review it directly.