Quick answers
- Is CVE-2026-24858 exploited in the wild?
- Yes. CVE-2026-24858 is known to be exploited in the wild, first recorded on 27 January 2026. Treat it as urgent.
- How severe is CVE-2026-24858?
- Critical severity, with a CVSS score of 9.8, published 27 January 2026.
- Which products and versions are affected?
- Fortinet Fortianalyzer 7.0.0 - 7.0.15, 7.2.0 - 7.2.11, 7.4.0 - 7.4.9, 7.6.0 - 7.6.5, 7.6.0 - 7.6.5, 7.4.0 - 7.4.9, 7.2.0 - 7.2.11, 7.0.0 - 7.0.15, 7.6.0 through 7.6.5, 7.4.0 through 7.4.9, 7.2.0 through 7.2.11, 7.0.0 through 7.0.15; Fortinet FortiManager 7.0.0 - 7.0.15, 7.2.0 - 7.2.11, 7.4.0 - 7.4.9, 7.6.0 - 7.6.5, 7.6.0 - 7.6.5, 7.4.0 - 7.4.9, 7.2.0 - 7.2.11, 7.0.0 - 7.0.15, 7.6.0 through 7.6.5, 7.4.0 through 7.4.9, 7.2.0 through 7.2.11, 7.0.0 through 7.0.15; Fortinet FortiNAC-F 7.6.3 through 7.6.5; Fortinet FortiOS 7.0.0 - 7.0.18, 7.2.0 - 7.2.12, 7.4.0 - 7.4.10, 7.6.0 - 7.6.5, 7.6.0 - 7.6.5, 7.4.0 - 7.4.10, 7.2.0 - 7.2.12, 7.0.0 - 7.0.18, 7.6.0 through 7.6.5, 7.4.0 through 7.4.10, 7.2.0 through 7.2.12, 7.0.0 through 7.0.18; and 4 more.
- Is there a fix for CVE-2026-24858?
- A patch was published on 2026-01-27: FortiCloud SSO re-enabled with enforcement to block vulnerable firmware versions. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-24858 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-24858?
- Check whether you run Apple Multiple Products, Fortinet Fortianalyzer, Fortinet FortiManager or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An Authentication Bypass Using an Alternate Path or Channel vulnerability [CWE-288] exists in the FortiCloud SSO implementation across multiple Fortinet product lines. The flaw allows an attacker who possesses a valid FortiCloud account and a registered device to authenticate as an administrator on other devices registered to different accounts, provided FortiCloud SSO is enabled. Exploitation does not require prior authentication to the target device. In the wild, attackers have been observed creating local administrative accounts and exfiltrating configuration files. Fortinet has since implemented server-side restrictions on FortiCloud to block vulnerable versions, but local firmware updates are required for full remediation.
Affected products
- Fortinet FortiAnalyzer 7.6.0 through 7.6.5, 7.4.0 through 7.4.9, 7.2.0 through 7.2.11, 7.0.0 through 7.0.15
- Fortinet FortiManager 7.6.0 through 7.6.5, 7.4.0 through 7.4.9, 7.2.0 through 7.2.11, 7.0.0 through 7.0.15
- Fortinet FortiOS 7.6.0 through 7.6.5, 7.4.0 through 7.4.10, 7.2.0 through 7.2.12, 7.0.0 through 7.0.18
- Fortinet FortiProxy 7.6.0 through 7.6.4, 7.4.0 through 7.4.12, 7.2.0 through 7.2.15, 7.0.0 through 7.0.22
- Fortinet FortiWeb 8.0.0 through 8.0.3, 7.6.0 through 7.6.6, 7.4.0 through 7.4.11
- Fortinet FortiNAC-F 7.6.3 through 7.6.5
- Fortinet FortiSwitchManager 7.2.0 through 7.2.8, 7.0.0 through 7.0.7
- Siemens RUGGEDCOM APE1808 (Fortigate NGFW) All versions with Fortinet NGFW < V7.4.11
Timeline
- 2026-01-22: other: Malicious FortiCloud accounts used in exploitation were locked out by Fortinet.
- 2026-01-26: other: Fortinet temporarily disabled FortiCloud SSO globally to protect customers.
- 2026-01-27: disclosed: Initial advisory publication.
- 2026-01-27: kev added: CISA added the vulnerability to the Known Exploited Vulnerabilities catalog.
- 2026-01-27: patched: FortiCloud SSO re-enabled with enforcement to block vulnerable firmware versions.