Skip to main content
Report · SecurityWeekAbout CVE-2026-24858Published

Fortinet Patches Exploited FortiCloud SSO Authentication Bypass

Source SecurityWeek

0
Authoritative record:CVE-2026-24858· Critical 9.4

Exploited in the wild · KEV due 30 Jan 2026 · patch available : patch FortiWeb now.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else.
Patch
Available
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H/RL:O/RC:C

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 27 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: evidence found.

    Listed in CISA KEV the same day as disclosure

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by fortinet

    , 4 hours before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 18 minutes after disclosure

  4. , the same day as disclosure

  5. KEV remediation due

    US federal deadline

    , 3 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
FortinetFortiWebAffected
  • >=8.0.0 <=8.0.3
  • >=7.6.0 <=7.6.6
  • >=7.4.0 <=7.4.11
Fixed in–
FortinetFortiNAC-FAffected
  • >=7.6.3 <=7.6.5
Fixed in–
FortinetFortiOSAffected
  • >=7.6.0 <=7.6.5
  • >=7.4.0 <=7.4.10
  • >=7.2.0 <=7.2.12
  • >=7.0.0 <=7.0.18
Fixed in–
FortinetFortiAnalyzerAffected
  • >=7.6.0 <=7.6.5
  • >=7.4.0 <=7.4.9
  • >=7.2.0 <=7.2.11
  • >=7.0.0 <=7.0.15
Fixed in–
FortinetFortiProxyAffected
  • >=7.6.0 <=7.6.4
  • >=7.4.0 <=7.4.12
  • >=7.2.0 <=7.2.15
  • >=7.0.0 <=7.0.22
Fixed in–
FortinetFortiManagerAffected
  • >=7.6.0 <=7.6.5
  • >=7.4.0 <=7.4.9
  • >=7.2.0 <=7.2.11
  • >=7.0.0 <=7.0.15
Fixed in–

AI-suggested

European organizations should immediately verify whether their Fortinet devices are registered with FortiCloud SSO and apply the official patches released by Fortinet to remediate CVE-2026-24858. Beyond patching, organizations should implement strict access controls and multi-factor authentication (MFA) for FortiCloud accounts to reduce the risk of unauthorized access. Regularly audit FortiCloud account activity and device login logs to detect anomalous or unauthorized access attempts. Network segmentation should be employed to limit the impact of any compromised devices. Additionally, organizations should review and tighten their identity and access management policies related to cloud-based device management platforms. Employing endpoint detection and response (EDR) tools to monitor for suspicious activity on Fortinet devices can provide early warning of exploitation attempts. Finally, maintain up-to-date incident response plans that include scenarios involving cloud-based authentication bypasses.

Description

Tracked as CVE-2026-24858, the bug allows attackers to log into devices registered to other FortiCloud accounts. The post Fortinet Patches Exploited FortiCloud SSO Authentication Bypass appeared first on SecurityWeek .

References

Community reviews

Loading reviews…