Fortinet - FortiCloud CVE‑2026‑24858 – What You Need to Know for Patching




 CVE‑2026‑24858 is a critical Fortinet vulnerability (CVSS 9.4–9.8) involving FortiCloud SSO authentication bypass, allowing attackers with a FortiCloud account to log into devices belonging to other customers if FortiCloud SSO is enabled.

This flaw affects FortiOS, FortiManager, FortiAnalyzer, and potentially FortiWeb and FortiSwitch Manager.

Attackers have been actively exploiting this vulnerability in the wild, creating rogue admin accounts, modifying firewall configs, enabling VPN access, and exfiltrating configuration files. 

CISA has added CVE‑2026‑24858 to the Known Exploited Vulnerabilities (KEV) catalog and requires patching by federal agencies by Jan 30 or Feb 17, 2026, depending on advisory.

Are Patches Available?

Yes—patches have been released for major product lines, but some versions still show “upcoming” in Fortinet’s advisory.

Released fixed versions (confirmed):

  • FortiOS:

    • 7.4.11 released
    • Future fixes: 7.6.6, 7.2.13, 7.0.19 (upcoming)
  • FortiManager:

    • Fix included in 7.4.10
    • Upcoming releases: 7.6.6, 7.2.13, 7.0.16
  • FortiAnalyzer:

    • Fix included in 7.4.10
    • Upcoming releases: 7.6.6, 7.2.12, 7.0.16
  • FortiProxy:

    • Fixes planned for 7.6.6 and 7.4.13
  • FortiWeb:

    • Still under investigation

A complete listing of affected versions and required upgrade paths appears in Fortinet’s PSIRT advisory. 


Mitigation Steps (Until Fully Patched)

Even before applying updates, Fortinet implemented server‑side protections:

1. FortiCloud SSO Logins Blocked for Vulnerable Devices

Fortinet has globally blocked SSO login from affected firmware versions until they are upgraded.
No client-side action is needed for blocking.

2. Emergency SSO Disablement & Re‑Enablement

FortiCloud SSO was:

  • Disabled on Jan 26
  • Re-enabled on Jan 27 with enforcement preventing vulnerable builds from authenticating

3. Recommended admin actions:

  • Restrict admin access
  • Check for rogue accounts (audit, backup, system, etc.)
  • Restore from known‑good configurations
  • Rotate credentials (including LDAP/AD tied to FortiGate)

4. Optional hardening

Disable FortiCloud SSO manually (CLI):

set admin-forticloud-sso-login disable

Popular posts from this blog

WSUS CVE-2025-59287 Mitigation

Cloud Infrastructures are Having a Bad Week

CVE-2025-58034 Fortinet Warnings and Mitigation