Back to Insights
  • SMB/SME
  • Enterprise

· Updated · ASC Editorial Team

Fortinet Publishes Its Advisories on 10 November: Patch Your FortiGates Before the Details Go Public

Update, 13 November 2026: Fortinet has published 46 advisories dated 10 November: eight critical, 37 high and one medium. Most affect FortiManager and FortiAnalyzer, and eight affect FortiOS. Fortinet lists none of them as known to be exploited, but NHS England's National CSOC now assesses exploitation as likely, because the details are public. Several critical flaws can be used without authentication by anyone who can reach a FortiManager's FGFM port or a FortiAnalyzer's OFTP port, so check that neither is reachable from the internet.

One advisory changes the advice below. FG-IR-26-219, rated 9.8, affects FortiManager and FortiAnalyzer 8.0 up to and including 8.0.2, and the fix will be in 8.0.3, which isn't released yet. Until it is, keep the JSON API disabled, which is the default, by setting rpc-permit to none on any administrator profile where it's enabled. Version 7.6.8 is fixed, and 7.4 and 7.2 aren't affected. A few high-severity advisories also list fixes in versions still to come, so check each advisory that applies to you rather than relying only on the version numbers below.

On 22 October 2026, Fortinet released a coordinated set of security updates for FortiOS, FortiManager and FortiAnalyzer, following earlier releases for FortiMail and FortiAuthenticator. The updates include critical and high-severity fixes for flaws found through its AI-assisted security testing. Fortinet published the advisories on its PSIRT page on Patch Tuesday, 10 November.

That date matters. Until then, the flaws' details weren't public. Fortinet's post doesn't say that any of them has been exploited. But it warns that AI tools can now help attackers reverse-engineer patches and build working exploits in hours or days rather than weeks. Fortinet's advice is to treat this as a priority change, not routine maintenance.

The minimum fixed versions for FortiOS are 8.0.2, 7.6.8, 7.4.13 and 7.2.14. FortiManager and FortiAnalyzer need 8.0.2, 7.6.8, 7.4.12 or 7.2.13 (but see the update above for 8.0). Note that the 7.4 and 7.2 numbers differ from FortiOS, so check each product separately. FortiMail needs 8.0.2, 7.6.7 or 7.4.9, and FortiMail 7.2 has to move to the 7.4 branch or later. FortiAuthenticator needs 8.0.4 or 6.6.11.

Start with an inventory. List every FortiOS instance and FortiManager, and put the internet-facing ones first. Don't assume a managed or cloud-hosted unit has been done: FortiSASE was updated automatically, but Fortinet says FortiManager Cloud may need a manual update and public cloud images follow each provider's release process.

Back up each configuration before upgrading, then follow Fortinet's supported upgrade path. Fortinet also advises watching the logs, before and after patching, for unusual administrator access or unapproved configuration changes.

If a device can't be upgraded straight away, reduce its exposure. Restrict HTTPS and SSH administration to trusted IP addresses, or turn them off on external interfaces, and make sure FortiManager can't be reached from the internet. Use strong, unique credentials and multi-factor authentication for every administrator. Fortinet is clear that these steps reduce risk but don't replace the upgrade.

Now that the advisories are public, read them against your inventory. They show which flaws apply to the features you run, and anyone looking for devices that haven't been patched can read them too.

If you had to name every Fortinet device you run and its version today, how long would it take?

Source: Fortinet: Fortinet Releases Security Hardening Release for Multiple Products

Get Insights by email

A short round-up of new articles every Monday morning. Nothing else.

We only keep your email address, and we don't track opens or clicks. Every email has an unsubscribe link. See our Privacy Notice.