Last updated: 13 November 2026. Sources are listed at the end.
Fortinet published 89 security advisories on 10 November 2026. One of them has a name: Fortinet2Shell, tracked as CVE-2026-121529. It is a critical flaw in FortiClient, the VPN and endpoint agent that offices with Fortinet firewalls usually install on every laptop. A web page the user opens in a browser can send commands to a FortiClient service running on the same PC, and that can end in code running on the machine.
Fortinet says it knows of no attacks using it. The fix is a FortiClient update, and there is no setting on the firewall that protects an unpatched laptop.
Not sure which laptops are still exposed? Emergency exposure check, ₹2,999, 48 hours. Send us up to 5 hosts or product versions and get a written verdict for each, what to patch first and how to verify the fix. Book the check or ask a question first.
The short answer
- Affected: FortiClient for Windows 7.4.0 to 7.4.7 and 7.2.0 to 7.2.14, FortiClient for Mac 7.4.0 to 7.4.7, and the FortiClient Windows PAM builds in the same ranges.
- Fixed in FortiClient 7.4.8 and 7.2.15. Version 8.0 is not affected. FortiClient for Mac 7.2 is not affected. Fortinet says the free VPN-only FortiClient for Windows is not impacted.
- The researcher who found it says it works reliably when FortiPAM is enabled on the client. Patch those PCs first.
- The user has to open a web page. According to the public analyses, no download or prompt is needed after that.
- Fortinet lists “Known exploited: No” as of 13 November. A proof-of-concept lab appeared on GitHub on 11 November, so do not plan on that staying true for long.
What Fortinet2Shell is
Fortinet’s advisory FG-IR-26-194 calls it an “origin validation error in local API endpoint” (CWE-346). FortiClient runs a small web service on the PC itself for its Privileged Access Agent, the part that works with FortiPAM. According to the write-ups by GBHackers and The CyberSec Guru, that service listens on TCP port 9191 by default.
A local service like this should only answer requests that come from FortiClient’s own components. This one did not check properly where a request came from. Kevin Joensen of Baldur Security, who reported the bug and named it, describes the root cause as a CORS misconfiguration: a page loaded from any website could talk to the local service through the user’s browser and read the answers.
Because the traffic never leaves the PC, your perimeter firewall and IPS do not see it. Fortinet’s advisory says the same thing in its own way: the “Virtual patch” field is “No”.
Fortinet scores it 9.1 on its advisory page. That figure includes Fortinet’s adjustment for exploit maturity and fix availability. The CVE record’s base score, as reported by The CyberSec Guru, is 9.6. Both are Critical.
Which FortiClient versions are affected
| Product | Affected | Fixed in |
|---|---|---|
| FortiClient Windows 7.4 | 7.4.0 to 7.4.7 | 7.4.8 or later |
| FortiClient Windows 7.2 | 7.2.0 to 7.2.14 | 7.2.15 or later |
| FortiClient Windows PAM 7.4 | 7.4.0 to 7.4.7 | 7.4.8 or later |
| FortiClient Windows PAM 7.2 | 7.2.0 to 7.2.14 | 7.2.15 or later |
| FortiClient Mac 7.4 | 7.4.0 to 7.4.7 | 7.4.8 or later |
| FortiClient Mac 7.2 | Not affected | |
| FortiClient 8.0 (Windows, Windows PAM, Mac) | Not affected |
Fortinet’s table does not list FortiClient 7.0 or older. A missing row is no proof that an old branch is safe. If you still run one, check Fortinet’s support lifecycle page and plan the move to a supported version.
Check your PCs
We have no FortiClient installation in our lab, so we have not run these commands against the product. They are standard Windows and macOS commands, and the port and process names come from the public write-ups. Run them only on machines you manage.
On Windows, show the installed FortiClient version in PowerShell:
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*',
'HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*' |
Where-Object DisplayName -like 'FortiClient*' |
Select-Object DisplayName, DisplayVersionThen see whether the Privileged Access Agent is listening and running:
Get-NetTCPConnection -LocalPort 9191 -State Listen -ErrorAction SilentlyContinue
Get-Process -Name FortiVRS -ErrorAction SilentlyContinueIf the version is in an affected range and either command returns a result, that PC goes to the top of the patch list. The port can be changed in EMS or FortiPAM, so an empty result on 9191 does not clear a machine by itself. The version number decides.
On a Mac, the equivalent checks are:
defaults read /Applications/FortiClient.app/Contents/Info.plist CFBundleShortVersionString
sudo lsof -nP -iTCP:9191 -sTCP:LISTENIf you manage clients through FortiClient EMS, its endpoint list already shows the FortiClient version of every enrolled device. That is faster than visiting each PC.
Fix it
- Upgrade FortiClient to 7.4.8 or later on the 7.4 branch, or 7.2.15 or later on the 7.2 branch. Push it from EMS if you have EMS. Otherwise download the installer from the Fortinet support portal and use your usual software deployment tool.
- Start with PCs where FortiPAM is in use, and with the laptops of admins and finance staff.
- Where nobody uses FortiPAM, The CyberSec Guru’s analysis suggests turning off the Privileged Access Agent in the EMS endpoint profile, which removes the local listener. Fortinet’s advisory lists no workaround, so treat this as a temporary extra step and still upgrade.
- Confirm the new version on a few machines with the commands above. A deployment report that says “success” is not the same as a version number.
Until a PC is patched, the usual advice applies with more weight than normal: keep the browser up to date and do not open links from unknown senders. Newer Chrome versions ask before a website may contact services on the local machine. The CyberSec Guru calls that partial protection, and it does not replace the update.
Signs that someone used it
Fortinet has published no indicators of compromise. The public analyses suggest these places to look if you have EDR or Sysmon logs:
- A browser process connecting to
127.0.0.1or::1on port 9191 shortly after the user visited an unfamiliar site. cmd.exe, PowerShell,rundll32.exeormshta.exestarted by the FortiClient processfortivrs.exe.- Before you reinstall a suspect machine, keep the FortiClient debug logs.
If you confirm that someone ran code on a company PC this way, report it. In India, unauthorised access to IT systems has to be reported to CERT-In within six hours of noticing it under the CERT-In Directions of 28 April 2022.
The other Fortinet fixes from 10 November
Fortinet2Shell got the headlines because it has a name. SecurityWeek counts nearly 100 vulnerabilities across the 89 advisories, about 17 of them critical and nearly 80 high. FortiMail has the largest group of critical fixes, followed by FortiAuthenticator, FortiOS, FortiManager and FortiAnalyzer. FortiSASE also received critical fixes.
Fortinet does not report attacks on any of them. Fortinet devices sit at the edge of the network and are a regular target once patches are public, so this batch should not wait for the next quarterly maintenance window. Open Fortinet’s PSIRT page, filter by the products you own, and compare the fixed versions with what you run. Our earlier guide on FortiMail CVE-2026-104286 covers a Fortinet bug that was exploited last month.
Free tool: See what your website shows to the internet with our website safety check. It grades your site in seconds.
Related guides
- FortiMail Vulnerability CVE-2026-104286 Exploited: Patch Now
- OpenSSH sshole (CVE-2026-123158): Check Your Alpine Servers
- Outlook Zero-Day CVE-2026-124194: November 2026 Patch Tuesday, What to Patch First
- Your Vendor Had a Data Breach: What to Do in the First 48 Hours
Sources
- Fortinet PSIRT FG-IR-26-194: Origin validation error in local API endpoint, 10 Nov 2026
- SecurityWeek: Fortinet Patches Nearly 100 Vulnerabilities, 11 Nov 2026
- GBHackers: Fortinet2Shell Vulnerability Lets Hackers Execute Code on FortiClient Systems Through Malicious Websites
- The CyberSec Guru: Fortinet2Shell CVE-2026-121529, FortiClient CORS RCE Flaw
- CERT-In Directions, 28 April 2022
Need help finding unpatched and exposed systems? Our VAPT services find them before attackers do, and the free website safety check grades your site in seconds. Contact us for a quote.
