CVE-2025-54973: Fortinet FortiAnalyzer · Improper access control
Affects Fortinet FortiAnalyzerSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N/E:X/RL:X/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Fortinet FortiAnalyzer | Affected
| Fixed in– |
AI-suggested
1. Monitor Fortinet’s official advisories and apply security patches promptly once released for the affected FortiAnalyzer versions. 2. Restrict network access to FortiAnalyzer management interfaces, especially FortiCloud SSO endpoints, using firewall rules and network segmentation to limit exposure to untrusted networks. 3. Enforce multi-factor authentication (MFA) for all administrative and user access to FortiAnalyzer to reduce the risk of unauthorized access even if the race condition is exploited. 4. Implement strict logging and monitoring of FortiCloud SSO authentication attempts, looking for anomalies or repeated failed attempts that may indicate exploitation attempts. 5. Conduct regular security audits and penetration testing focused on authentication mechanisms and race condition vulnerabilities. 6. Educate security teams about this vulnerability to ensure rapid detection and response to suspicious activity related to FortiCloud SSO. 7. Consider deploying additional endpoint and network detection tools to identify lateral movement or unusual behavior stemming from compromised FortiAnalyzer access. 8. If possible, temporarily disable FortiCloud SSO integration until patches are applied or additional controls are in place to mitigate risk.
Description
A concurrent execution using shared resource with improper synchronization ('Race Condition') vulnerability [CWE-362] in Fortinet FortiAnalyzer version 7.6.0 through 7.6.2, 7.4.0 through 7.4.6, 7.2.0 through 7.2.10 and before 7.0.13 allows an attacker to attempt to win a race condition to bypass the FortiCloud SSO authorization via crafted FortiCloud SSO requests.