11/16/2026 • Security
FortiOS HA Flaw: When Firewalls Trust Each Other Too Much
Fortinet has patched CVE-2026-126259, a critical FortiOS flaw where crafted high-availability packets can run commands as super admin with no login. It only applies to specific HA setups, so here is how to check whether yours is one of them and what to do.
On 10 November 2026, Fortinet published a fix for a FortiOS flaw in which the firewall will take commands, at the highest privilege level it has, from a network packet that never proves who sent it. The catch is where that packet has to arrive: on the channel FortiGates use to keep each other in sync.
The flaw is tracked as CVE-2026-126259 (Fortinet advisory FG-IR-26-273). It is rated Critical, there is no sign of it being exploited, and it applies only to particular high-availability configurations. All three of those facts matter, so let us take them in turn.
What happened, in plain English
Businesses that cannot afford a firewall outage often run two or more FortiGates together. The units constantly exchange high-availability (HA) traffic so that each one knows the other's state and configuration and can take over if its partner fails.
Fortinet's advisory describes the problem as missing authentication for a critical function (CWE-306). In the affected configurations, FortiOS does not properly check that HA packets come from a genuine peer. An attacker who can get crafted HA packets to the device can execute commands as super admin, with no username, password or user interaction required.
The nuances, as confirmed against Fortinet and the US National Vulnerability Database (NVD):
- It is unauthenticated. The CVSS vector lists privileges required as none (PR:N). This is not one of those flaws where the attacker needs a login first.
- It only applies to specific setups. The advisory names two: FGSP (FortiGate Session Life Support Protocol) clustering with
standalone-config-syncenabled, or autoscale deployments, which are typically found in cloud environments. A single standalone FortiGate does not fit the conditions Fortinet describes. - The severity score needs a footnote. NVD carries Fortinet's base score of 9.8. Fortinet's own advisory page shows 9.0, which is the same rating adjusted for the fact that no exploit is known and an official fix exists. Both are Critical.
- Reachability is the real limiter. Fortinet titles the advisory as adjacent command execution via HA, while the formal CVSS vector rates it as network-reachable. In practice, the attacker has to be able to deliver HA packets to the firewall. If that traffic is confined to a dedicated link, the opportunity is small. If it shares a network with other things, it is not.
- It is not known to be exploited. Fortinet marks it as not exploited, and it is not on CISA's Known Exploited Vulnerabilities list as of 16 November 2026. NVD's record was still awaiting its own analysis on that date.
- Fortinet found it themselves. The advisory credits Fortinet's Product Security team, working with the help of an AI model. A vendor finding its own bug before attackers do is the good version of this story.
Affected versions and fixes
| FortiOS branch | Affected | What to do |
|---|---|---|
| 8.0 | 8.0.0 | Upgrade to 8.0.1 or later |
| 7.6 | 7.6.0 to 7.6.7 | Upgrade to 7.6.8 or later |
| 7.4 | 7.4.0 to 7.4.12 | Upgrade to 7.4.13 or later |
| 7.2 | 7.2.0 to 7.2.13 | Upgrade to 7.2.14 or later |
| 7.0 | All versions | Migrate to a fixed release |
Note the last row. Fortinet lists no fixed build on the 7.0 branch, so if you are still on 7.0 the answer is a move to a newer branch, not a point release. The advisory also mentions a virtual patch delivered through Fortinet's signature updates for those who cannot upgrade straight away, but it lists no configuration workaround.
The real lesson: the back channel counts too
Most security attention goes to the front door: the admin login page, the VPN portal, anything facing the internet. This flaw sits somewhere quieter. The sync channel between firewalls was built on the assumption that whatever is at the other end is a trusted partner.
That assumption turns up all over a network. Cluster links, management VLANs, switch stacking ports and backup interfaces are all channels that devices use to talk among themselves, and they tend to get far less scrutiny than anything user-facing. They also carry a lot of power, precisely because the devices on them trust each other.
If an attacker is already inside, perhaps through a phished laptop or a forgotten device nobody is watching, these internal channels are how a small foothold becomes control of the firewall itself. It is worth knowing where yours are and what else can reach them.
The honest bit
Fortinet has had a busy year for advisories, and we covered one of the bigger ones in our FortiBleed explainer. It would be easy to turn this into a pile-on, and it would be unfair. No vendor is immune, including the ones we like and sell. Every firewall maker has shipped critical flaws, and here Fortinet found the problem internally, published clear version guidance and released fixes on the day.
The one difference worth mentioning is how the fix reaches you. With a traditionally managed firewall, someone has to notice the advisory, schedule the upgrade and carry it out, and on a cluster that takes planning. Platforms where the vendor delivers firmware updates for you shorten that gap. That is not a reason to rip anything out. It is a reason to be sure somebody owns patching, whichever platform you run.
What we'd suggest you actually do
- Find out whether you run HA at all. If you have one FortiGate on its own, the conditions in the advisory do not describe you. Still check your version, because other fixes arrive in the same releases.
- If you do, check which kind. Ask your IT provider whether the setup uses FGSP with
standalone-config-sync, or an autoscale deployment in the cloud. Those are the configurations Fortinet names. - Check your FortiOS version against the table above and schedule the upgrade. Fortinet's upgrade path tool will tell you the supported steps between versions.
- On 7.0? Start planning the move now. There is no fixed 7.0 build listed, so this needs a proper migration window, not a quick patch.
- Look at where HA traffic travels. Sync and heartbeat interfaces belong on dedicated links or an isolated network segment that staff devices, guest Wi-Fi and the internet cannot reach. That is sound practice with or without this flaw.
- Keep the basics in order. Unique admin credentials, MFA on management access, and some way of noticing unusual behaviour on the network.
The friendly takeaway
For most small businesses running a single FortiGate, this one is a prompt to check and move on. For anyone running the affected HA configurations, it is a patch to schedule soon, while it is still a quiet advisory and not a headline. Either way, nobody is known to be exploiting it, and the fix is available today.
If you are not sure which camp you are in, or you would like a second pair of eyes on how your firewalls are set up, get in touch. We are happy to help you work it out, with no hard sell.
References
- Fortinet PSIRT advisory FG-IR-26-273, Unauthenticated adjacent command execution via HA: https://fortiguard.fortinet.com/psirt/FG-IR-26-273
- NVD entry for CVE-2026-126259: https://nvd.nist.gov/vuln/detail/CVE-2026-126259
- CVE record for CVE-2026-126259: https://www.cve.org/CVERecord?id=CVE-2026-126259
- CISA Known Exploited Vulnerabilities Catalog (checked 16 November 2026, not listed): https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Fortinet upgrade path tool: https://docs.fortinet.com/upgrade-tool