CVE-2026-24858: An Authentication Bypass Using an Alternate Path or Channel vulnerability [CWE-288] vulnerability in Fortin...
An Authentication Bypass Using an Alternate Path or Channel vulnerability [CWE-288] vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.5, FortiAnalyzer 7.4.0 through 7.4.9, FortiAnalyzer 7.2.0 through 7.2.11, FortiAnalyzer 7.0.0 through 7.0.15, FortiManager 7.6.0 through 7.6.5, FortiManager 7.4.0 through 7.4.9, FortiManager 7.2.0 through 7.2.11, FortiManager 7.0.0 through 7.0.15, FortiNAC-F 7.6.3 through 7.6.5, FortiOS 7.6.0 through 7.6.5, FortiOS 7.4.0 through 7.4.10, FortiOS 7.2.0 through 7.2.12, FortiOS 7.0.0 through 7.0.18, FortiProxy 7.6.0 through 7.6.4, FortiProxy 7.4.0 through 7.4.12, FortiProxy 7.2.0 through 7.2.15, FortiProxy 7.0.0 through 7.0.22, FortiWeb 8.0.0 through 8.0.3, FortiWeb 7.6.0 through 7.6.6, FortiWeb 7.4.0 through 7.4.11 may allow an attacker with a FortiCloud account and a registered device to log into other devices registered to other accounts, if FortiCloud SSO authentication is enabled on those devices.
Security readout for executives and security teams
Plain-English summary
CVE-2026-24858 is a critical Fortinet authentication bypass affecting multiple Fortinet security products when FortiCloud SSO is enabled. A person with a FortiCloud account and registered device may be able to access devices registered to other accounts. Because CISA lists it as known exploited, affected environments should treat this as urgent.
Executive priority
Treat this as an emergency Fortinet remediation item. It affects security infrastructure, has a critical score, and is KEV-listed. Prioritize assets with FortiCloud SSO enabled and management interfaces reachable from untrusted networks.
Technical view
The issue is CWE-288, authentication bypass using an alternate path or channel. Affected ranges include FortiOS, FortiManager, FortiAnalyzer, FortiProxy, FortiWeb, and FortiNAC-F. The CVSS 3.1 score is 9.4 with network access, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is highest where affected Fortinet versions use FortiCloud SSO. The bundle does not prove exposure for devices without FortiCloud SSO enabled. Internet-facing administration or broadly reachable management planes would increase business risk.
Exploitation context
Active exploitation is supported by the CISA KEV reference in the source bundle. Fortinet also published analysis of SSO abuse on FortiOS. The bundle does not include exploit mechanics, affected tenant counts, or confirmed exploitation against every listed product.
Researcher notes
The key exposure condition is FortiCloud SSO enabled on affected versions. The source bundle supports broad product impact and active exploitation, but does not provide safe validation probes, exploit details, or complete fixed-version mapping in the supplied text.
Mitigation direction
Identify affected Fortinet products and versions across the environment.
Confirm whether FortiCloud SSO is enabled on each device.
Apply Fortinet PSIRT fixed releases or vendor-approved workarounds for FG-IR-26-060.
If upgrade is delayed, assess disabling FortiCloud SSO using vendor guidance.
Restrict administrative access paths and review FortiCloud SSO authentication monitoring.
Validation and detection
Compare deployed versions against the affected ranges in CVE-2026-24858.
Verify FortiCloud SSO configuration per device and account.
Check CISA KEV status for required remediation handling.
Review authentication logs for unexpected FortiCloud SSO access.
Confirm remediation against Fortinet PSIRT FG-IR-26-060.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-288: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-288 · source CWE mapping
Authentication Bypass Using an Alternate Path or Channel
Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.