FortiCloud SSO bypass: when fully patched is not enough
Attackers got into fully patched FortiGate firewalls through a cloud login that registering a device can switch on. What to turn off, and what to watch.
Published · 3 min read

On 22 January Fortinet confirmed that attackers were signing in to FortiGate firewalls through FortiCloud single sign-on, including firewalls fully upgraded to the latest release at the time. That pointed to a new way in, not the two December flaws the latest release had fixed. The flaw, later CVE-2026-24858, let someone with their own FortiCloud account and a registered device log in to devices registered to other accounts, wherever FortiCloud SSO was switched on. And it could be on without anyone deciding so: registering a firewall with Fortinet from the device's own screen turns it on, unless the administrator clears a toggle on the registration page.
The attacks had begun by 15 January, when the security firm Arctic Wolf started seeing automated logins followed within seconds by the same steps: new generic accounts for persistence, VPN access for those accounts, and the firewall's configuration exported. Fortinet found that in almost all cases the attacker created a local administrator, with names such as audit, backup, itadmin, secadmin and support. It locked the two FortiCloud accounts doing it, switched FortiCloud SSO off on 26 January, and on 27 January published its advisory, the last fixed releases following on 30 January; the service has refused logins from vulnerable versions since. CISA listed the flaw as exploited on 27 January.
Patched, and still open
Some of the firewalls in this story had done what every checklist asks: they ran the latest firmware. What let the attackers in was a convenience login that went through the vendor's cloud rather than the firewall's own accounts, one that registration could switch on as a side effect. A patch fixes the code you run. It does not switch off a feature you did not know was on, and it does not tell you who signed in through it.
The exported configuration is the other half of the damage. It holds the firewall's accounts, usually with their passwords in hashed form, and Arctic Wolf warns that attackers crack such hashes offline, especially weak ones, so its advice was to treat them as compromised and reset them. Fortinet went further where its indicators were found: treat the configuration as compromised, restore a known clean version, and change credentials, including any directory accounts connected to the firewall.
What it means for systems with single sign-on
I connect systems to single sign-on, through Auth0 and SAML, and nothing here is an argument against it: Fortinet confirmed that third-party SAML identity providers were not affected, only its own cloud login. The lesson is about counting the ways in. A business system can have a password screen, a sign-in button for the office's accounts, an API key for another system and a support login for whoever maintains it. Each is a door, and the one that causes trouble is the one nobody remembers opening.
For each door I would want three answers written down: who can use it, who is told when someone does, and how it is shut. A new administrator account in particular should never be quiet. In this attack Fortinet saw one created in almost all cases, and it showed in the firewall's own log.
Five checks for your firewall
- List the cloud and remote-management features switched on in your firewall and other network devices, and turn off any you do not use. On a FortiGate this one is the setting "Allow administrative login using FortiCloud SSO".
- Do not allow administration from the open internet. Fortinet's own best practice is a separate management connection, and failing that, a short list of known addresses.
- Review every administrator account on every device, and remove any that nobody can explain. Names like support and backup are easy to overlook.
- Send administrator sign-ins and new administrator accounts to someone who reads them the same day.
- If a device was reached, restore a clean configuration and change every credential it held, including connected directory accounts.
The same count of doors applies to the systems behind the firewall, and if yours have never had one, the fit check is a good place to start.
Sources
- Arctic Wolf, Arctic Wolf Observes Malicious Configuration Changes On Fortinet FortiGate Devices via SSO Accounts, 21 January 2026
- Fortinet, Analysis of Single Sign-On Abuse on FortiOS, 22 January 2026
- FortiGuard Labs, Administrative FortiCloud SSO authentication bypass, 27 January 2026
- Cybersecurity and Infrastructure Security Agency, CISA Catalog of Known Exploited Vulnerabilities
Enrique Lacambra III builds internal business systems from Cainta, Rizal.
Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.
