Fortinet has released fixes and advisory FG-IR-26-060 for CVE-2026-24858, a critical authentication bypass (CWE-288) in FortiCloud single sign-on. Attackers exploited it as a zero-day in January 2026. Anyone with a FortiCloud account and a registered device could log in to devices belonging to other customers, provided FortiCloud SSO administrative login was enabled on the target.
What happened
From mid-January, Arctic Wolf and others reported a wave of automated intrusions into FortiGate firewalls through FortiCloud SSO. Attackers created administrator accounts with VPN access and downloaded full device configurations within seconds of logging in. Reported indicators included the account [email protected] and the IP 104.28.244.114. Some of the compromised devices were already running releases patched for the earlier SSO flaws CVE-2025-59718 and CVE-2025-59719.
Fortinet’s timeline:
- 22 January: identified exploitation by two malicious FortiCloud accounts and disabled them
- 23 January: confirmed a new attack path, not a bypass of the earlier patch
- 26 January: disabled FortiCloud SSO on the cloud side as an emergency measure
- 27 January: published the advisory and fixed releases, and re-enabled SSO with stricter checks that reject logins from devices still running vulnerable versions
CISA added the CVE to its KEV catalog with a short remediation deadline for federal agencies.
Who is affected
FortiOS, FortiManager, FortiAnalyzer and FortiProxy devices with FortiCloud SSO login enabled are affected. The feature is off by default, but registering a device with FortiCare through the GUI turns it on unless the administrator clears the option. Most outlets report a CVSS score of around 9.4.
Recommendations
- Upgrade to the fixed releases listed in FG-IR-26-060. Until then, disable SSO admin login. On FortiOS/FortiProxy:
config system globalthenset admin-forticloud-sso-login disable. On FortiManager/FortiAnalyzer:config system samlthenset forticloud-sso disable. - Audit for recently created local admin accounts, especially ones with names that look like system accounts, and for new VPN users.
- Assume exported configurations are compromised. Rotate VPN pre-shared keys, local passwords, LDAP/RADIUS bind credentials and certificates.
- Restrict management interfaces to trusted networks and send admin login events to your SIEM.