CVE-2026-24858 lets an attacker who controls any FortiCloud account use FortiCloud single sign-on to log into other customers' FortiOS, FortiManager, FortiAnalyzer, FortiProxy, FortiWeb and FortiNAC-F devices; Fortinet found it exploited in the wild, disabled FortiCloud SSO network-wide to contain it, and CISA added it to KEV the same week, though the 9.8 CVSS figure is Fortinet's own CNA score rather than an NVD Primary rating.
Vulnerability summary
CVSS base score
9.8
Critical severity
EPSS score (FIRST)
86.6%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
Yes
Listed as known exploited
Published
Vulnerability ID: CVE-2026-24858 · Source: Fortinet PSIRT (CVSS not NVD-confirmed)
Affected components
| Component | CPE | Version range |
|---|---|---|
| Fortinet FortiOS | cpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:* | 7.0.0 through 7.0.18; 7.2.0 through 7.2.12; 7.4.0 through 7.4.10; 7.6.0 through 7.6.5 |
| Fortinet FortiManager | cpe:2.3:a:fortinet:fortimanager:*:*:*:*:*:*:*:* | 7.0.0 through 7.0.15; 7.2.0 through 7.2.11; 7.4.0 through 7.4.9; 7.6.0 through 7.6.5 |
| Fortinet FortiAnalyzer | cpe:2.3:a:fortinet:fortianalyzer:*:*:*:*:*:*:*:* | 7.0.0 through 7.0.15; 7.2.0 through 7.2.11; 7.4.0 through 7.4.9; 7.6.0 through 7.6.5 |
| Fortinet FortiProxy | cpe:2.3:a:fortinet:fortiproxy:*:*:*:*:*:*:*:* | 7.0.0 through 7.0.22; 7.2.0 through 7.2.15; 7.4.0 through 7.4.12; 7.6.0 through 7.6.4 |
| Fortinet FortiWeb | cpe:2.3:a:fortinet:fortiweb:*:*:*:*:*:*:*:* | 7.4.0 through 7.4.11; 7.6.0 through 7.6.6; 8.0.0 through 8.0.3 |
| Fortinet FortiNAC-F | cpe:2.3:a:fortinet:fortinac-f:*:*:*:*:*:*:*:* | 7.6.3 through 7.6.5 |
What does this mean for affected devices?
CVE-2026-24858 is an Authentication Bypass Using an Alternate Path or Channel (CWE-288) in Fortinet's FortiCloud single sign-on feature. Fortinet's PSIRT advisory FG-IR-26-060 states that "malicious actors with a FortiCloud account and a registered device [can] log in to separate devices registered to other users" across FortiOS, FortiManager, FortiAnalyzer, FortiProxy, FortiWeb, FortiSwitch Manager and FortiNAC-F when FortiCloud SSO is enabled on the target device (Fortinet PSIRT FG-IR-26-060).
Fortinet states the vulnerability "was found being exploited in the wild by two malicious FortiCloud accounts, which were locked out on 2026-01-22," and that it temporarily disabled all FortiCloud SSO authentication on 2026-01-26 before reinstating it on 2026-01-27 with changes intended to block the exploitation path. This followed two related, previously disclosed FortiCloud SSO bypass issues (CVE-2025-59718 and CVE-2025-59719); Fortinet notes patching those earlier bugs alone does not remediate CVE-2026-24858 (Fortinet PSIRT FG-IR-26-060).
CISA added CVE-2026-24858 to the Known Exploited Vulnerabilities catalog on 2026-01-27, with a required-action due date of 2026-01-30, listing the affected vendor/project as Fortinet across FortiAnalyzer, FortiManager, FortiOS and FortiProxy; known ransomware campaign use is recorded as "Unknown" (CISA KEV).
NVD's record for this CVE shows status "Analyzed," but the only CVSS entry on file is a CVSS v3.1 score of 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) submitted by Fortinet's own PSIRT ([email protected]) and marked Secondary — NVD has not published an independent Primary CVSS metric for this CVE as of this check. This page therefore attributes the 9.8 score to Fortinet PSIRT rather than labeling it NVD-confirmed, while still indexing the page because KEV presence alone is independently sufficient grounds under our publishing rules (NVD).
Fortinet's recommended remediation is to apply the patched build appropriate to each affected product (via the upgrade path listed at docs.fortinet.com) or, as an immediate mitigation, disable FortiCloud SSO login for the device under System Settings or via the CLI. FIRST EPSS currently scores the probability of exploitation at 0.8659 (99.7th percentile) as of 2026-10-30, consistent with a cross-tenant authentication bypass with confirmed in-the-wild abuse (FIRST EPSS).
Evidence
- FortiCloud SSO authentication bypass lets an attacker with any FortiCloud account and registered device log into other users' devices across FortiOS, FortiManager, FortiAnalyzer, FortiProxy, FortiWeb, FortiSwitch Manager and FortiNAC-F when FortiCloud SSO is enabled. — Fortinet PSIRT FG-IR-26-060
- Found exploited in the wild via two malicious FortiCloud accounts locked out on 2026-01-22; Fortinet briefly disabled all FortiCloud SSO authentication (2026-01-26 to 2026-01-27) to contain it; patching the earlier CVE-2025-59718/CVE-2025-59719 bypasses does not remediate this issue. — Fortinet PSIRT FG-IR-26-060
- Added to the CISA KEV catalog on 2026-01-27, due date 2026-01-30, known ransomware use Unknown. — CISA KEV
- NVD vulnStatus is Analyzed, but the only CVSS metric present (3.1, 9.8) is sourced from [email protected] and marked type Secondary; no NVD Primary CVSS metric exists for this CVE. — NVD
- EPSS score is 0.8659 (99.7th percentile) as of 2026-10-30. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Did patching the earlier FortiCloud SSO bugs already fix CVE-2026-24858?
No. Fortinet explicitly states that patching the previously disclosed CVE-2025-59718 and CVE-2025-59719 bypasses does not remediate CVE-2026-24858; it requires its own fix (per Fortinet PSIRT FG-IR-26-060).
How did Fortinet respond when it found this being exploited?
Fortinet identified two malicious FortiCloud accounts exploiting the flaw, locked them out on 2026-01-22, and temporarily disabled all FortiCloud SSO authentication network-wide from 2026-01-26 to 2026-01-27 while deploying changes to block the exploitation path (per Fortinet PSIRT FG-IR-26-060).
Is there an immediate mitigation besides installing the patched build?
Yes. Fortinet's advisory recommends disabling FortiCloud SSO login for the device under System Settings or via the CLI as an immediate mitigation if the patched build can't be applied right away (per Fortinet PSIRT FG-IR-26-060).
Is the 9.8 CVSS figure confirmed by NVD's own analysts?
No. NVD's record shows status Analyzed, but the only CVSS entry on file is Fortinet PSIRT's own Secondary submission; NVD has not published an independent Primary metric (per NVD).
Which Fortinet products does this bypass reach?
Any device with FortiCloud SSO enabled across FortiOS, FortiManager, FortiAnalyzer, FortiProxy, FortiWeb, FortiSwitch Manager and FortiNAC-F (per Fortinet PSIRT FG-IR-26-060).
Questions about this page?