News ·

FortiGate Users: Check This HA Cluster Setting Now

Fortinet has disclosed a critical flaw in the high-availability (HA) feature of FortiOS, tracked as CVE-2026-126259. HA traffic lacks authentication, and in certain deployments an attacker who has not logged in can run commands with super-admin rights. Businesses running FortiGate pairs or clusters should check their firmware versions and HA settings soon.

Who is at risk? According to Fortinet advisory FG-IR-26-273 (published 10 November, updated 16 November), the highest-risk setups are devices using FGSP together with standalone-config-sync, or using autoscale. There, crafted HA packets can lead to command execution as super admin. Ordinary FGCP clusters, both active-passive and active-active, are also affected on unpatched versions, but the attacker must be able to reach the HA heartbeat segment. Fortinet rates the issue 9.0 (CVSSv3), while the US National Vulnerability Database (NVD) scores it 9.8. The advisory lists no known exploitation in the wild, and the issue was found by Fortinet's own security team.

Affected and fixed versions: 8.0.0 should move to 8.0.1 or later; 7.6.0 to 7.6.7 to 7.6.8 or later; 7.4.0 to 7.4.12 to 7.4.13 or later; and 7.2.0 to 7.2.13 to 7.2.14 or later. Every 7.0 release is affected and there is no fix on that branch, so those devices need to migrate to a fixed release line. Check the upgrade path with Fortinet's official upgrade tool first rather than jumping several versions at once.

Upgrading is not the whole story. Fortinet advises that where the HA layer-2 segment is not fully trusted, fixed versions should also have an HA password set, with encryption and authentication enabled. Standalone-config-sync with FGSP peers additionally needs encryption and a pre-shared key on the standalone cluster, and autoscale needs its own pre-shared key. Fortinet also offers a virtual patch, FG-VD-61445.0day, in FMWP database update 26.082, which may be worth evaluating until the upgrade is done.

A five-point self-check: First, log in to every FortiGate, note the FortiOS version and compare it with the fixed releases above. Second, confirm the HA mode (FGCP, FGSP or autoscale) and whether standalone-config-sync is enabled. Third, make sure HA heartbeat ports are directly connected or on a dedicated VLAN, not sharing switch ports with office or guest networks. Fourth, confirm the HA password, encryption and authentication are all on, and that pre-shared keys are not defaults or weak passwords. Fifth, plan the upgrade: back up the configuration, pick a maintenance window, follow the official path step by step, and afterwards test session sync and failover. Devices still on 7.0 need a migration plan as early as possible.

This article is an industry briefing, published in November 2026; Fortinet's official advisory takes precedence. Kunshan Tingyun provides day-to-day firewall operations for businesses and is glad to help review HA settings or schedule an upgrade if needed.

Sources

  1. Fortinet PSIRT advisory FG-IR-26-273, “Unauthenticated adjacent command execution via HA” (CVE-2026-126259), published 10 November 2026, updated 16 November 2026: https://fortiguard.fortinet.com/psirt/FG-IR-26-273
  2. GitHub Advisory Database, GHSA-f2f6-qwmc-g833 (CVE-2026-126259, includes the NVD 9.8 score), 12 November 2026: https://github.com/advisories/GHSA-f2f6-qwmc-g833