FortiGate Admin Login Bypass (CVE-2026-24858): The Audit Checklist I Run on My Own Firewall

A FortiGate admin login bypass sounds like a problem for people who left a setting wide open. CVE-2026-24858 is more awkward than that. FortiCloud SSO is off on a factory-default FortiGate, but it switches itself on when you register the device to FortiCare through the GUI, unless you turn off the toggle on that screen. A firewall can end up with it enabled without anyone having decided to.

I run FortiOS 7.6 on a FortiGate 81F-POE, so the menus and commands below follow that branch. Other supported branches use the same steps with a different fixed version.

Last reviewed: 20 November 2026.

Advertisement

What the FortiGate admin login bypass is

CVE-2026-24858 is an authentication bypass in FortiCloud single sign-on, with a CVSS score of 9.4. When FortiCloud SSO login is enabled, an attacker who has a FortiCloud account and a registered device of their own can log in to devices registered to other customers. CISA described it that way in its guidance. FortiOS, FortiManager, FortiAnalyzer and FortiProxy are affected.

It followed two earlier FortiCloud SSO bugs, CVE-2025-59718 and CVE-2025-59719, which Fortinet patched in December 2025. Admins then reported intrusions on devices that already had that patch, and on 22 January 2026 Fortinet confirmed the attacks used a separate flaw. It disabled the abused FortiCloud accounts that day, switched FortiCloud SSO off globally on 26 January, and brought it back on 27 January with a block on devices running vulnerable firmware.

Affected admins described attackers logging in through FortiCloud SSO with the address cloud-init@mail.io and then creating new local admin accounts. The audit section below looks for exactly that pattern.

How to check if the FortiGate admin login bypass applies to you

Two things decide your exposure: the firmware version and whether FortiCloud SSO login is on.

Check the firmware version

Run this on the CLI and read the Version line:

get system status

Compare it with the fixed FortiOS releases. Any version at or above the number in the table is fixed.

FortiOS branchFixed in
7.67.6.6
7.47.4.11
7.27.2.13
7.07.0.19

FortiOS 6.4 is listed as unaffected.

Check the FortiCloud SSO toggle

In the GUI, go to System > Settings and look at “Allow administrative login using FortiCloud SSO”. From the CLI:

show full-configuration system global | grep forticloud-sso

If the output says enable, the feature is on.

Patch FortiOS first

Back up the configuration before upgrading and store the file somewhere access-controlled. A FortiGate config holds VPN users, pre-shared keys and certificates. Check the supported upgrade path for your current version, then move to 7.6.6 or later on the 7.6 branch.

Fortinet’s cloud-side change means FortiCloud SSO no longer accepts logins from devices on vulnerable versions, and its advice was to upgrade to a fixed release. Patching remains the main fix.

Disable FortiCloud SSO if nobody uses it

If your team logs in with local admin accounts, FortiCloud SSO gives you nothing and leaves one more way in. Fortinet said that, although only FortiCloud SSO abuse had been seen, the issue applies to all SAML SSO implementations, so admins might want to turn it off. In the GUI, switch off “Allow administrative login using FortiCloud SSO” under System > Settings. In the CLI:

config system global
    set admin-forticloud-sso-login disable
end

Before you log out, confirm that a local admin account works. Otherwise you can lock yourself out of your own firewall.

Audit admin accounts and logs

Patching closes the hole. It does not tell you whether someone used it before you patched.

Advertisement
  1. Open System > Administrators, or run show system admin in the CLI. Look for accounts that you or your team did not create, especially recent ones.
  2. Open Log & Report > System Events and look for SSO logins. Search for cloud-init@mail.io and for the source addresses 37.1.209.19 and 217.119.139.50, which were reported as indicators in Fortinet’s analysis.
  3. For any SSO login you find, check what happened afterwards: configuration downloads, privilege changes and new admin accounts.

Fortinet warned that a device showing these indicators should be treated as fully compromised. In practice that means isolating it, restoring a known-good configuration, and rotating every admin, VPN and service credential the firewall held. Fortinet’s PSIRT analysis carries the current indicator list, so check it instead of relying on the two addresses here. A search with no results does not prove the device is clean.

Lock down admin access

These settings limit the damage from the next admin login bug as well as this one.

  • Restrict each admin account to your management subnet with trusted hosts. Replace the example subnet with yours.
  • Remove HTTPS and SSH from the allowed access list on WAN interfaces, so the admin interface is not reachable from the internet.
  • Turn on multi-factor authentication for admin accounts.
  • Subscribe to Fortinet PSIRT advisories so you hear about new issues on the day they are published.
config system admin
    edit "your-admin-name"
        set trusthost1 192.168.1.0 255.255.255.0
    next
end

If you find a breach: PDPA in Malaysia

A firewall configuration can expose VPN usernames and other personal data. Since 1 June 2025, Malaysia’s PDPA has required data controllers to notify the Personal Data Protection Commissioner as soon as practicable once they have reason to believe a personal data breach has occurred. Whether your incident meets that bar is a question for your data protection officer or legal adviser. This post is not legal advice.

FAQ

Is FortiCloud SSO enabled by default on a FortiGate?

No, it is off in factory settings. It switches on automatically when an admin registers the device to FortiCare through the GUI, unless the “Allow administrative login using FortiCloud SSO” toggle is turned off during registration.

Which FortiOS versions fix CVE-2026-24858?

FortiOS 7.6.6, 7.4.11, 7.2.13 and 7.0.19 or later. FortiOS 6.4 is not affected.

Do I still need to disable FortiCloud SSO after patching?

Fortinet said disabling it on the device was not necessary once it blocked vulnerable versions on the cloud side. If nobody on your team uses FortiCloud SSO, turning it off still removes one login path. Confirm a local admin login works first.

Does this affect FortiManager and FortiAnalyzer?

Yes, along with FortiProxy. Fixed FortiManager releases are 7.6.6, 7.4.10, 7.2.13 and 7.0.16. Fixed FortiAnalyzer releases are 7.6.6, 7.4.10, 7.2.12 and 7.0.16. On both, you can turn the feature off under System Settings > SAML SSO, or with set forticloud-sso disable under config system saml.

How do I know if my FortiGate was compromised through FortiCloud SSO?

Check the administrator list for accounts you did not create, then search the system event logs for the reported indicators: the cloud-init@mail.io login and the two source addresses listed above. Any match means you should treat the device as compromised.

Conclusion

Four checks cover this FortiGate admin login bypass: firmware at or above the fixed release, the FortiCloud SSO toggle, the administrator list, and the system event logs. Run them on every FortiGate, FortiManager and FortiAnalyzer you manage, then subscribe to Fortinet PSIRT so the next advisory reaches you on the day it is published.

Sources

Leave a Comment