Fortinet FortiAnalyzer
CVE-2025-54973
MEDIUM
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach FortiAnalyzer SSO endpoint
-
ExploitSend crafted concurrent FortiCloud SSO requests
-
ExecutionWin race against auth check
-
ImpactBypass FortiCloud SSO authorization
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation specifically requires that FortiAnalyzer be configured to use FortiCloud SSO authentication and that the attacker can reach the SSO request interface over the network. The attacker must win a timing-sensitive race condition (CWE-362) in the SSO authorization logic by issuing crafted, concurrent FortiCloud SSO requests, which is reflected as HIGH attack complexity (AC:H). Exploitation is further LIMITED by required user interaction (UI:R) - a legitimate/victim SSO action or concurrent flow is needed - and by the non-default dependency on FortiCloud SSO being enabled; deployments using only local authentication are not in scope. Affected builds are FortiAnalyzer 7.6.0-7.6.2, 7.4.0-7.4.6, 7.2.0-7.2.10, and all versions before 7.0.13. |
| Impact | This is a moderate-severity, lower-priority issue rather than a top-tier emergency. The official CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N, base 5.3) describes a network-reachable, unauthenticated flaw but with HIGH attack complexity (AC:H) - inherent to CWE-362 race conditions, which require precise timing to win - and it also requires user interaction (UI:R), both of which materially reduce real-world exploitability. The EPSS score is low (0.32%, 22nd percentile), consistent with no observed widespread exploitation activity. The vulnerability is NOT listed in CISA KEV, and no public exploit (POC) is referenced, so exploitation status is 'no public exploit identified at time of analysis.' These signals are mutually consistent: a race-condition SSO authorization bypass that is hard to win and needs user interaction is a plausible targeted-attack avenue but not a mass-exploitation candidate. One notable inconsistency to flag: for an 'authorization bypass' one would typically expect a confidentiality impact (C), yet the vendor vector sets C:N and only I:H - this likely reflects that winning the race lets an attacker assert/alter an authorization state (integrity of the auth decision) rather than directly reading data; verify the precise impact scope with Fortinet advisory FG-IR-25-198 before downgrading or upgrading priority. Overall: real but conditional risk, appropriate for scheduled patching rather than immediate incident response, barring exposure of FortiAnalyzer management/SSO interfaces to untrusted networks. |
| Exploit ScenarioDerived | An attacker with network reachability to a FortiAnalyzer FortiCloud SSO interface sends a burst of crafted FortiCloud SSO requests timed to coincide with a legitimate user's SSO action, racing the improperly synchronized authorization check to slip through as an authorized session. Because the CVSS vector specifies high attack complexity and required user interaction, success depends on precise timing and a concurrent victim SSO flow. No public proof-of-concept exploit has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
An unauthenticated race condition (CWE-362) in Fortinet FortiAnalyzer's FortiCloud SSO authorization logic lets a remote attacker attempt to win a timing-sensitive race and bypass SSO authorization by sending crafted, concurrent FortiCloud SSO requests. Affected builds are 7.6.0 through 7.6.2, 7.4.0 through 7.4.6, 7.2.0 through 7.2.10, and all versions before 7.0.13, and the flaw only matters where FortiCloud SSO is actually configured - deployments using purely local authentication are out of scope. Rated CVSS 5.3 (AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N) with EPSS around 0.32% (22nd percentile), this is a moderate-severity, lower-priority issue rather than a top-tier emergency, and there is no public exploit identified at time of analysis.
RemediationAI
Apply the Fortinet fixed release for your branch as documented in PSIRT advisory FG-IR-25-198 (https://fortiguard.fortinet.com/psirt/FG-IR-25-198) - for the 7.0 branch this means moving to 7.0.13 or later, and for the 7.2, 7.4, and 7.6 branches upgrading beyond the affected ranges (7.2.0-7.2.10, 7.4.0-7.4.6, 7.6.0-7.6.2) to the corresponding patched maintenance releases listed in the advisory. Patch status is vendor-released per the advisory; verify exact fixed build numbers against FG-IR-25-198 before upgrading. Because exploitation depends on FortiCloud SSO being enabled, the most effective compensating control is to disable FortiCloud SSO and use local authentication (or another SSO provider) until the upgrade is applied - at the trade-off of losing centralized FortiCloud identity management. Additionally, restrict network access to the FortiAnalyzer management and SSO-facing interfaces to trusted management networks or VPN, which reduces both this race window and general exposure, though it does not eliminate the flaw for authorized clients. Monitor authentication logs for anomalous or repeated FortiCloud SSO authorization events as a detection measure while remediation is pending. There is no public exploit identified at time of analysis, so prioritization can follow normal patch cycles rather than emergency response.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is a classic race condition - concurrent execution using a shared resource with improper synchronization (CWE-362) - within the FortiCloud SSO authorization flow of FortiAnalyzer. Because FortiCloud SSO involves a multi-step, stateful exchange (redirect, token/assertion handling, session establishment) shared across concurrent requests, the short window between validation and session/authorization commit can be exploited if an attacker interleaves crafted FortiCloud SSO requests. The CVSS vector reflects a network-reachable attack (AV:N) that is nonetheless high-complexity (AC:H) because winning a race is timing-dependent, and it requires user interaction (UI:R) - a legitimate SSO action or concurrent flow must occur - while no privileges are needed beforehand (PR:N). Impact is scoped to integrity (I:H), specifically bypassing the SSO authorization decision (consistent with the Authentication Bypass tag), with no direct confidentiality or availability impact. The four CPE entries (cpe:2.3:a:fortinet:fortianalyzer) confirm the affected product family across multiple version branches. The non-default precondition that FortiCloud SSO must be enabled significantly narrows the exposed population relative to a general FortiAnalyzer compromise.
Know when Fortianalyzer gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
Network-reachable SSO interface (AV:N) with no prior auth (PR:N); race condition and need for a concurrent victim SSO action drive AC:H and UI:R; bypassing authorization compromises integrity (I:H) without direct data read (C:N) or availability loss.
Primary rating from Vendor (fortinet).
CVSS VectorVendor: fortinet
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).
Affected Products (CPE)CVE.org
More in Fortianalyzer
View allA buffer underwrite ('buffer underflow') vulnerability in the administrative interface of Fortinet FortiOS version 7.2.0
A client-side enforcement of server-side security [CWE-602] vulnerability in Fortinet FortiManager version 7.4.0 and bef
An improper neutralization of special elements used in an os command ('OS Command Injection') vulnerability [CWE-78] in
A server-side request forgery vulnerability [CWE-918] in Fortinet FortiAnalyzer version 7.4.0, version 7.2.0 through 7.2
Remote code execution in Fortinet FortiManager and FortiAnalyzer (plus their Cloud variants) arises from a stack-based b
Authenticated low-privileged users can exploit an SQL injection flaw in Fortinet FortiAnalyzer and FortiAnalyzer Cloud t
A client-side enforcement of server-side security in Fortinet FortiAnalyzer-BigData at least version 7.4.0 and 7.2.0 thr
A improper handling of insufficient permissions or privileges in Fortinet FortiAnalyzer version 5.6.0 through 5.6.11, Fo
An improper neutralization of input vulnerability in FortiAnalyzer before 6.4.1 and 6.2.5 may allow a remote authenticat
An improper certificate validation vulnerability [CWE-295] in FortiAnalyzer and FortiManager 7.2.0 through 7.2.1, 7.0.0
Local privilege escalation in Fortinet FortiAnalyzer, FortiManager and their Cloud variants allows an already-authentica
Local privilege escalation in Fortinet FortiManager (6.4.0-6.4.14, 7.0.0-7.0.12, 7.2.0-7.2.5, 7.4.0-7.4.3) and FortiAnal
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB