An administrator assigned to one virtual domain on Fortinet’s management or analysis systems may be able to reach another through the HTTP API. Fortinet’s November 10 advisory identifies the defect as CVE-2026-126229 and rates it critical, with a CVSS 3.1 score of 9.1. It affects FortiManager and FortiAnalyzer, including their Cloud variants.
The prerequisite is a signed-in administrator. Fortinet describes the consequence as allowing “an authenticated administrator to access to other VDOMs via specially crafted HTTP requests.” That access can undermine the separation teams expect when they delegate administration by virtual domain. Fortinet lists known exploitation as “No” and says its own product security team discovered the issue internally, with Loic Pantano credited for the report.
An administrator crosses VDOM access
A VDOM separates administrative control between domains on a system. Fortinet identifies a user-controlled key in dmserver (CWE-639) as the authorization bypass and names the API as the affected component. It lists virtual patch availability as “No,” so plan the branch upgrade.
The Fortinet-authored CVE record also lists the affected products and version ranges in structured form. Its score requires high privileges and assigns changed scope because an authenticated administrator can reach another VDOM. Inventory the running FortiManager, FortiAnalyzer and Cloud builds against the affected ranges below.
Check each product’s installed branch
For on-premises FortiManager and FortiAnalyzer, Fortinet lists 8.0.0–8.0.1, 7.6.0–7.6.7, 7.4.0–7.4.11 and 7.2.0–7.2.12 as affected. In the Cloud variants, the affected 8.0 build is 8.0.1; the affected 7.6 range is 7.6.0–7.6.7, while 7.4 starts at 7.4.1 and 7.2 starts at 7.2.1. Each product’s entire 7.0 branch requires migration to a fixed release. Match the deployed product as well as its branch before choosing a target: the Cloud starting versions differ from on-premises.
Fortinet’s first fixed releases for the 8.0, 7.6, 7.4 and 7.2 branches are 8.0.2, 7.6.8, 7.4.12 and 7.2.13, respectively, for all four product families. Fortinet lists no 7.0 maintenance fix; migrate to a fixed branch. For provider-managed Cloud tenants, confirm the deployed build in the tenant administration view or with the provider.
Upgrade and confirm the running build
Inventory the FortiManager and FortiAnalyzer systems where administrators work across separate VDOMs, including Cloud deployments, and compare the running version with the product’s affected row. Upgrade or migrate affected systems to the corresponding fixed release. Until then, limit which administrators can reach these management APIs and review who holds administrative access; this reduces the number of people who can exercise the authenticated path, but the release change is the remedy Fortinet specifies.
After the change, read the running build on each affected installation or Cloud tenant and compare it with the applicable fixed version above. Keep the product and build together in the change record: Cloud 8.0 starts at 8.0.1, while on-premises 8.0 starts at 8.0.0. If investigating possible cross-VDOM access, preserve local administrative and API records and review administrator activity against VDOM assignments. Fortinet’s advisory supplies no request signature, so use those records to reconstruct earlier access.