Fortinet has widened its advisory for a critical FortiOS flaw that can let an attacker on a firewall cluster's high-availability network segment run commands as super admin without logging in. An update posted on November 16 says FortiGate HA clusters running FGCP, in both active-passive and active-active modes, are also affected on unpatched versions.
The bug, tracked as CVE-2026-126259 in Fortinet's advisory FG-IR-26-273, is a missing authentication check on a critical function (CWE-306) and carries a CVSS v3 score of 9.0. The original advisory, published November 10, described an unauthenticated attacker executing commands as super admin via crafted HA packets on setups using FGSP with standalone-config-sync, or autoscale. Fortinet lists the flaw as not known to be exploited. It was published the same day as the critical FortiOS and FortiMail fixes we covered last week.
The attacker has to be on the HA segment
High availability (HA) links are the connections that let paired or clustered firewalls share configuration and session state so one can take over if another fails. Fortinet stresses that exploitation requires an attack vector adjacent to that HA segment, so this is not a bug an attacker can trigger from the open internet. Fortinet's own guidance focuses on environments where the HA Layer 2 segment is not fully trusted.
The November 16 update matters because FGCP is Fortinet's standard clustering protocol. The first version of the advisory named only FGSP with standalone-config-sync and autoscale deployments, so administrators of ordinary FGCP pairs may have concluded they were out of scope.
Upgrade to 7.6.8, 7.4.13 or 7.2.14, then lock down HA
Fortinet's fixed releases are:
- FortiOS 8.0.0: upgrade to 8.0.1 or above
- FortiOS 7.6.0 through 7.6.7: upgrade to 7.6.8 or above
- FortiOS 7.4.0 through 7.4.12: upgrade to 7.4.13 or above
- FortiOS 7.2.0 through 7.2.13: upgrade to 7.2.14 or above
- FortiOS 7.0, all versions: migrate to a fixed release
Where the HA segment is not fully trusted, Fortinet says to harden the link on fixed versions as well. For FGCP clusters, in either mode, and for standalone-config-sync without FGSP peers, set an HA password and enable both encryption and authentication under the "config system ha" settings. Standalone-config-sync with FGSP peers needs the same, plus encryption and a pre-shared secret under "config system standalone-cluster". Autoscale deployments should set a pre-shared secret under "config system autoscale". Fortinet has also released a virtual patch, named FG-VD-61445.0day, in FMWP database update 26.082.
Another flaw found with an AI model
Fortinet credits Theo Leleu of its Product Security team, who found the bug internally with the use of the frontier AI model Claude Mythos. That continues a run of AI-assisted internal finds in Fortinet's advisories this autumn.
Internal discovery means no outside attacker is known to have had a head start. But the advisory and the fixed builds are now public, and the people best placed to reach an HA segment are the ones already inside the network.
This briefing is provided by IntelFusions for informational and defensive purposes only. It is based on sources assessed to be reliable at the time of writing, and analytic judgments carry the confidence levels indicated. Indicators of compromise are defanged; re-arm them only in controlled environments. IntelFusions is not affiliated with the organizations named and makes no warranty as to completeness or accuracy.