Skip to content
Security alerts

FortiOS patches for November 2026: CVE-2026-126259 and two more critical flaws, versions to install

FortiOS patches of 10 November 2026: CVE-2026-126259 (HA), CVE-2026-126253 (OSPF), CVE-2026-126254 (BGP). Versions 8.0.2, 7.6.8, 7.4.13, 7.2.14 and checks to run.

By the ALLSAFE SOLUTIONS engineering team19 November 20265 min read
Secured server room

The short answer: on 10 November 2026, Fortinet published the detailed advisories for the flaws fixed by its October hardening release. For FortiOS, the operating system of FortiGate firewalls, three flaws are rated critical: CVE-2026-126259 (command execution through the high availability link), CVE-2026-126253 (authentication bypass in OSPF) and CVE-2026-126254 (an error in BGP). Fortinet reports no exploitation, and CISA has not added any of them to its catalogue. The versions to install are FortiOS 8.0.2, 7.6.8, 7.4.13 or 7.2.14. Morocco’s maCERT (DGSSI) rated this batch at a critical risk level on 12 November.

We flagged this hardening release in our October FortiMail alert, when the CVE identifiers were not yet public. They now are: anyone can read what these versions fix, attackers included. This alert sticks to Fortinet’s advisories, the NVD, CISA and the maCERT bulletin.

What is affected in FortiOS

Product Affected versions Fixed version
FortiOS 8.0 8.0.0 through 8.0.1 8.0.2 or above
FortiOS 7.6 7.6.0 through 7.6.7 7.6.8 or above
FortiOS 7.4 7.4.0 through 7.4.12 7.4.13 or above
FortiOS 7.2 7.2.0 through 7.2.13 7.2.14 or above
FortiOS 7.0 and 6.4 all versions migrate to a fixed release

Sources: Fortinet advisories FG-IR-26-273, FG-IR-26-267, FG-IR-26-268 and FG-IR-26-193, maCERT bulletin 70971211/26. For each branch, the table gives the version that fixes all three critical flaws at once. Fortinet points to its upgrade path tool for intermediate steps.

The three critical flaws, one by one

CVE and advisory Component What the flaw allows CVSS score published by Fortinet
CVE-2026-126259, FG-IR-26-273 High availability Command execution as super admin, without authentication, through crafted HA packets 9.0
CVE-2026-126253, FG-IR-26-267 OSPF daemon Broadcasting routing advertisements (LSA) by an unauthenticated attacker 9.3
CVE-2026-126254, FG-IR-26-268 BGP daemon A configured iBGP neighbour sending malformed attributes to all connected routers; stated impact: denial of service 9.6

Three details from the advisories:

  • CVE-2026-126259 targets FGSP setups with standalone configuration sync, and autoscale. Fortinet adds that FGCP clusters, active-passive and active-active alike, are also affected on vulnerable versions, but that the attack requires access to the network segment of the HA link. The NVD entry, still awaiting analysis, shows a score of 9.8 supplied by Fortinet for this flaw, while the advisory states 9.0.
  • CVE-2026-126254 requires an already configured iBGP neighbour: the attack starts from a trusted device, not from the internet.
  • FortiSASE is also affected by the OSPF and BGP flaws; Fortinet states it remediated the service in version 26.3.2, with no customer action.

The other fixes not to overlook

The same batch fixes high-severity FortiOS flaws, two of which deserve an SME’s attention:

  • CVE-2026-121528 (FG-IR-26-193, score 7.7): improper certificate validation in the SSL VPN web portal, which may allow interception between the portal and the destination website. Fixed in 7.6.5, 7.4.10 and 7.2.14; FortiOS 8.0 is not affected.
  • CVE-2026-126258 (FG-IR-26-272, score 7.1): buffer overflow in the WAD proxy, which can crash proxy or ZTNA sessions. Only versions 8.0.0 and 7.6.7 are affected.

The maCERT bulletin also covers FortiManager, FortiAnalyzer, FortiAuthenticator, FortiSandbox, FortiMail, FortiVoice, FortiRecorder and FortiPAM. If you run any of these products, refer to Fortinet’s 10 November advisories for each one’s fixed version.

Severity and exploitation

  • Published severity: critical for all three flaws according to Fortinet; critical risk and impact levels according to maCERT.
  • Exploitation: not confirmed. The advisories state “Known Exploited: No”, and none of these flaws appears in the CISA KEV catalogue in its 18 November 2026 version.
  • Origin: discovered internally by Fortinet’s product security team, according to the advisories.

Interim and hardening measures

For the high availability flaw, Fortinet asks you, on a fixed version and where the HA segment is not fully trusted, to enable:

config system ha
   set password <secret>
   set encryption enable
   set authentication enable
end

With FGSP peers, add encryption and a pre-shared key under config system standalone-cluster; with autoscale, a pre-shared key under config system autoscale.

If the upgrade has to wait a few days:

  • Virtual patches: Fortinet lists a virtual patch for CVE-2026-126259 (“FG-VD-61445.0day”, FMWP database 26.082) and for CVE-2026-126254 (“FG-VD-62507.0day”, FMWP database 26.118). The OSPF advisory offers none.
  • Isolated HA link: heartbeat interfaces should stay on a direct cable or a dedicated VLAN, with no other device.

Checks to run

  • Record the version of every FortiGate, including the passive member of a cluster and units at remote sites.
  • Identify the affected setups: FGCP cluster, FGSP, autoscale, OSPF, BGP, SSL VPN web portal, proxy and ZTNA.
  • Check the HA link: dedicated cabling, password set, encryption and authentication enabled after the upgrade.
  • Review OSPF and BGP: neighbour authentication, passive interfaces wherever no neighbour is expected, BGP neighbours limited to known devices.
  • Spot the 7.0 and 6.4 branches, which require a migration, not a simple upgrade.

Our reading for businesses in Morocco

Two of these flaws concern dynamic routing, found mostly at carriers and in large networks. The third concerns high availability, which many businesses use: a cluster of two FortiGates whose heartbeat link crosses a shared switch is exactly the targeted case. Our guide to the FortiGate high availability cluster recalls how to cable and upgrade a cluster without downtime, and our method to upgrade FortiOS safely applies as is: backup, upgrade path, maintenance window, planned rollback. As a Fortinet integrator in Morocco, we apply these versions first on exposed devices.

How we can help

We inventory your FortiGates, apply the fixed version for your branch in a controlled maintenance window, harden the HA link and routing, then provide 24/7 monitoring, with critical incidents handled in under 15 minutes. See our approach to business cybersecurity in Morocco, then request your free initial audit: we reply within 24 business hours.

Sources: Fortinet advisories FG-IR-26-273, FG-IR-26-267, FG-IR-26-268, FG-IR-26-193 and FG-IR-26-272, maCERT bulletin 70971211/26, CISA KEV catalogue, NVD CVE-2026-126259, NVD CVE-2026-126253, NVD CVE-2026-126254.

Frequently asked questions

Are these FortiOS flaws being exploited?

Not so far, according to official sources. Fortinet advisories FG-IR-26-273, FG-IR-26-267 and FG-IR-26-268 state “Known Exploited: No”, and none of these flaws appears in the CISA KEV catalogue in its 18 November 2026 version. Now that the details are public, the time before a possible exploit shrinks: the upgrade should not wait.

My FortiGate is not in a cluster: am I affected?

Yes, by the version to install. CVE-2026-126259 targets high availability and autoscale setups, but the same version also fixes the OSPF and BGP flaws, an SSL VPN flaw and other high-severity flaws. A standalone FortiGate with no dynamic routing is still affected by those other fixes.

Which FortiOS version should I install?

FortiOS 8.0.2, 7.6.8, 7.4.13 or 7.2.14 depending on your branch, or a later version. The 7.0 and 6.4 branches receive no fix for these flaws: Fortinet asks you to migrate to a fixed release, following the upgrade path given by its tool.

Is upgrading enough for the high availability flaw?

Fortinet asks for one more step when the network segment of the HA link is not fully trusted: on a fixed version, set an HA password and enable encryption and authentication under config system ha, and a pre-shared key for FGSP and autoscale setups.

About the editorial team

ALLSAFE SOLUTIONS

Network, security and cloud engineers

Written by the engineering team at ALLSAFE SOLUTIONS, a managed IT provider founded in Casablanca by network, security and cloud engineers. Our articles draw on the projects we deliver for clients in Morocco and abroad.

LinkedIn

This guide is part of our expertise in business cybersecurity in Morocco: free initial audit, reply within one business day.

← All articles
CallWhatsAppFree audit