Cybersecurity

FortiManager and FortiOS: eight critical Fortinet advisories worth patching now

Fortinet published eight critical advisories on 10 November, with CVSS scores of up to 9.8, affecting FortiManager, FortiAnalyzer, FortiOS and FortiSASE. None has confirmed active exploitation yet, but six of the eight don't need a password to be exploited, and FortiManager and FortiAnalyzer are the pieces that control and log your whole FortiGate fleet.

What happened

On 10 November, Fortinet published eight critical security advisories, with CVSS scores between 9.0 and 9.8, affecting FortiManager, FortiAnalyzer, FortiOS and FortiSASE. Six of the eight flaws don't require the attacker to be authenticated. Fortinet found almost all of them internally, and so far none is listed as actively exploited.

These are the two that should worry an SME with a FortiGate the most:

  • CVE-2026-126261 (CVSS 9.0). An authorisation flaw in the FGFM protocol, the one FortiManager uses to talk to your FortiGate devices, lets anyone who can reach that port execute commands without the device's registration password ever being verified.
  • CVE-2026-126253 (CVSS 9.3). An authentication flaw in the OSPF daemon of FortiOS and FortiSASE lets an unauthenticated attacker broadcast forged routes, if you have OSPF enabled between sites.

The most serious of the eight, CVE-2026-126170 (CVSS 9.8), is in FortiManager and FortiAnalyzer's JSON-RPC API, but that API ships disabled by default: it only affects you if you've enabled it yourself.

Who it affects

If your FortiGates are managed from a FortiManager -common in a managed service-, the FGFM flaw affects you simply by having that port reachable, without you having enabled anything. If you use OSPF between sites, check the second flaw too. The other advisories in the batch depend on what you have deployed and enabled (FortiAnalyzer, the JSON-RPC API, BGP, or high availability with standalone-mode or autoscale synchronisation): check each one on Fortinet's PSIRT portal.

What to do, step by step

  1. Check your version. In FortiOS, all of branch 7.0, 7.2 (up to 7.2.13), 7.4 (up to 7.4.12), 7.6 (up to 7.6.7) and 8.0 (up to 8.0.1) are affected by the OSPF flaw. In FortiManager, 7.2 (up to 7.2.8), 7.4 (up to 7.4.5), 7.6 (up to 7.6.7) and 8.0.0 are affected by the FGFM flaw.
  2. Update. For the OSPF flaw, upgrade FortiOS to 7.2.14, 7.4.13, 7.6.8 or 8.0.2 (or migrate if you're on the 7.0 branch). For the FGFM one, upgrade FortiManager to 7.2.9, 7.4.6, 7.6.8 or 8.0.1.
  3. Check the rest of the batch before considering yourself up to date. Some fixes, such as FortiManager's fix for one of the high-availability flaws, were still listed as "upcoming" when this report was written: check the specific advisory on Fortinet's PSIRT portal.
  4. If you can't update yet, check that your FortiManager's FGFM and OFTP ports aren't reachable from the internet -they never should be- and disable the JSON-RPC API in admin profiles if you don't use it.

Important: FortiManager and FortiAnalyzer see and control your whole FortiGate fleet. A flaw there doesn't stay on one device: it spreads to every one it manages.

How we can help

As a Fortinet partner, we review the versions of your FortiGate, your FortiManager and your FortiAnalyzer, apply the updates or mitigations that fit each case, and check that the management ports aren't left exposed to the internet.

More news

Other news that may affect your IT.