Check these three things.
-
System owner: confirm each FortiManager runs its version group's fixed release or above, such as 8.0.1 for the 8.0 group.
Fixed release for each version group
- Provider: confirm the release of any FortiManager it runs for you.
- FortiManager versions belong to version groups named by their first two numbers. For example, 7.4.5 is in the 7.4 group.
- Fortinet lists these affected releases and fixes for CVE-2026-126261:
- 8.0 group: 8.0.0 is affected. Update to 8.0.1 or above.
- 7.6 group: 7.6.0 through 7.6.7 are affected. Update to 7.6.8 or above.
- 7.4 group: 7.4.0 through 7.4.5 are affected. Update to 7.4.6 or above.
- 7.2 group: 7.2.0 through 7.2.8 are affected. Update to 7.2.9 or above.
- The CVE record lists FortiManager only. It marks releases outside these ranges as unaffected.
- These releases fix CVE-2026-126261. Two related high-privilege flaws need later releases in some groups.
- Record:
- Installed release.
- Source of that record.
- Date checked.
- An installed fix does not show whether the FortiManager was reached before the update.
-
Network owner: confirm which networks can reach each FortiManager's FGFM service, which is separate from its web sign-in page.
When the risk applies
- No account is needed. Reach to the FGFM service is the condition.
- FGFM is the service FortiManager uses to manage FortiGate firewalls. Fortinet's Device Manager uses it to add devices and install policy packages and device settings.
- Affected interface:
- Fortinet's advisory summary and the CVE record name the FGFM port as the required path.
- The advisory's component field says GUI. The sources do not explain this label.
- A reachable web sign-in page does not show that FGFM is reachable.
- A blocked web sign-in page does not show that FGFM is blocked.
- Still unknown until checked: which networks can reach FGFM on each FortiManager.
- Fortinet's FortiManager 7.6 incoming-ports list names TCP/541 for IPv4 FGFM management. Confirm the port your deployment uses.
- Fortinet documents FGFM designs that place FortiManager on the public internet. Only your records show whether yours is reachable.
- Records to check:
- Firewall rules in front of the FortiManager.
- NAT and port-forwarding rules.
- Cloud network access rules, if hosted in a cloud.
- Provider statements, if a provider hosts it.
- Limited FGFM reach lowers exposure. An affected release needs the fix even so.
-
Security owner: review existing FortiManager records for unexpected management changes or managed-device activity.
What the records can show
- Records to review:
- Existing FortiManager administrator logs.
- Existing FortiManager event logs.
- Devices added or provisioned.
- Policy packages installed.
- Device settings installed.
- Changes on managed FortiGates that no approved change explains.
- Cover the period when an affected release was reachable, including FortiManagers updated since.
- Limits:
- Fortinet's advisory gives no specific signs of attack.
- A clean log is not proof of no change.
- A missing log leaves the question unresolved.
- An update does not rule out earlier harm.
- Records to review:
If an affected FortiManager's FGFM service is reachable from untrusted networks, update it first. Review its management records even after the update.