Fortinet says an unauthorized remote attacker may execute unauthorized code or commands, but successful exploitation requires victim interaction.Fortinet assigns CVSS 3.1 a 9.1 Critical score with user interaction required. Security teams can use a vulnerability intelligence platform to track affected client builds and remediation status. The CVE record does not describe the exact interaction or entry point.
What it allows
How Could CVE-2026-121529 Lead to Code Execution?
Fortinet classifies the weakness as an origin validation error. Its CVE record says a remote attacker needs no prior privileges, but the victim must interact before unauthorized code or commands may run. The record does not describe the interaction, endpoint, or execution context, so teams should not assume a specific browser or email attack path.
The CVSS vector rates confidentiality, integrity, and availability impacts as high. That is Fortinet's severity assessment, not evidence of an observed compromise. For context on the outcome, see the remote code execution definition.
How Should Defenders Interpret Current Risk?
As of November 14, 2026, five public GitHub repositories matched a search for CVE-2026-121529. This is a repository count, not a count of validated exploits or incidents. CISA's November 13 KEV catalog did not list the CVE, so the exploitation status remains unknown.
The public repository count and KEV status do not establish an incident. Check installed FortiClient products and versions against Fortinet's affected ranges before prioritizing remediation.
Who is affected
Version Check
| Release Line | Affected Range | Fixed In |
|---|---|---|
| 7.4.x | 7.4.0 to before 7.4.8 | 7.4.8 |
| Release Line | Affected Range | Fixed In |
|---|---|---|
| 7.2.x | 7.2.0 to before 7.2.15 | 7.2.15 |
| 7.4.x | 7.4.0 to before 7.4.8 | 7.4.8 |
For distribution packages and custom builds, check the supplier’s advisory.
FortiClientWindowsPAM has only two specifically named affected versions, 7.2.14 and 7.4.7. Check those releases manually against the Fortinet record.
Which FortiClient Versions Are Affected by CVE-2026-121529?
Fortinet lists FortiClientMac 7.4.0 through 7.4.7 and FortiClientWindows 7.4.0 through 7.4.7 as affected. It also lists FortiClientWindows 7.2.0 through 7.2.14. For FortiClientWindowsPAM, the record names only versions 7.4.7 and 7.2.14 as affected.
The CVE record lists FortiClientMac 7.4.8 or 8.0.0 and above as upgrade targets. For FortiClientWindows and FortiClientWindowsPAM, it lists 7.2.15, 7.4.8, or 8.0.0 and above for their respective branches. Do not treat the WindowsPAM single-version entries as a continuous affected range.
What Should Teams Verify After Updating?
Inventory installed FortiClient products by operating system, product name, and full version. Prioritize endpoints on the affected releases, including devices outside the normal management group. Apply the relevant Fortinet upgrade and confirm the installed client reports the expected fixed build after maintenance.
Keep the asset and verification result in the patch management process. If an endpoint still reports an affected build, repeat the update or investigate why deployment failed. Review available endpoint and user activity around suspicious interactions, while treating anomalies as leads for investigation.
Timeline
-
2026-11-10
Fortinet published the CVE record with affected and fixed releases.
-
2026-11-13
Fortinet updated the CVE record; the record does not identify a specific changed field.
What to do
-
Inventory FortiClient installations
Record the product name, operating system, and full installed version for each endpoint. Separate FortiClientWindowsPAM from FortiClientWindows before comparing affected releases.
-
Update affected client branches
Upgrade FortiClientMac 7.4 to 7.4.8 or 8.0.0 and above. Upgrade affected FortiClientWindows 7.2 builds to 7.2.15 and affected 7.4 builds to 7.4.8. For WindowsPAM, update the specifically listed 7.2.14 and 7.4.7 builds to their corresponding fixed releases; Fortinet also lists 8.0.0 and above.
-
Verify the installed build
After maintenance, check the endpoint's installed client version against the applicable fixed release. Recheck devices that missed deployment and retain the verification result.
-
Review suspicious endpoint activity
Investigate unusual endpoint or user activity around unexpected interactions on affected devices. This is Brandefense defensive guidance; the CVE record does not provide a specific detection signature.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-121529 in Brandefense Atlas
The Atlas record of CVE-2026-121529: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-121529 require victim interaction?
Yes. Fortinet says successful exploitation requires interaction with the victim. Its CVE record does not describe the exact interaction.
Which FortiClientWindows versions need an upgrade?
Fortinet lists 7.2.0 through 7.2.14 and 7.4.0 through 7.4.7 as affected. The listed upgrade targets are 7.2.15, 7.4.8, or 8.0.0 and above, depending on branch.
Is FortiClientWindowsPAM affected across both entire branches?
The CVE record specifically names WindowsPAM 7.2.14 and 7.4.7 as affected. It does not describe the whole 7.2 or 7.4 branch as affected.
Does a GitHub repository count prove active exploitation?
No. A GitHub search returned five public repositories as of November 14, 2026. Search results do not verify exploit functionality or an incident.
Sources
- CVE-2026-121529 RecordFortinet CNA via CVE Program
- Known Exploited Vulnerabilities CatalogCISA