FortianalyzerApplication · Fortinet
CVE-2025-54973
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFortiAnalyzer versions 7.0 through 7.6.2 contain a race condition (CWE-362) in the FortiCloud SSO authorization mechanism. An authenticated attacker can send crafted SSO requests and attempt to win the race condition to bypass authorization controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FortianalyzerApplication
>= 7.0.9, < 7.0.14>= 7.2.0, < 7.2.11>= 7.4.0, < 7.4.7>= 7.6.0, < 7.6.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify FortiAnalyzer versionAccess the FortiAnalyzer CLI or web UI and retrieve the current firmware version. In CLI, this is typically shown via 'get system status' or 'fnsysctl get system status' commands. In the web UI, check the Dashboard or System Settings for the firmware version.Affected if The installed version falls within any of these ranges: 7.0.9 through 7.0.13, 7.2.0 through 7.2.10, 7.4.0 through 7.4.6, or 7.6.0 through 7.6.2. Versions outside these ranges (including 7.0.14+, 7.2.11+, 7.4.7+, 7.6.3+) are not affected.
-
Confirm FortiCloud SSO is configuredCheck the FortiAnalyzer configuration for FortiCloud SSO or SAML SSO settings. In CLI, this is typically found under 'user fortianalyzer' or 'user saml' configuration blocks, or via 'show user fortianalyzer' and 'show user saml' commands. In the web UI, check under User & Authentication > User Definition or Single Sign-On settings.Affected if A FortiCloud SSO or SAML SSO configuration exists and is enabled. The vulnerability only applies when this feature is actively configured and in use.
-
Review SSO authentication logsExamine FortiAnalyzer logs for SSO authentication events. In the web UI, go to Log View > User > Authentication or use the CLI 'execute log filter' to review SSO-related events. Look for patterns of repeated SSO authorization attempts or anomalies in authentication flows.Affected if Evidence of repeated SSO authorization attempts, unexpected authorization bypasses, or authentication anomalies is present in the logs. This may indicate active exploitation attempts.
You are affected if your FortiAnalyzer version is 7.0.9-7.0.13, 7.2.0-7.2.10, 7.4.0-7.4.6, or 7.6.0-7.6.2 AND FortiCloud SSO is enabled in your environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.0.147.2.117.4.7
Apply vendor-supplied patches: upgrade to FortiAnalyzer 7.6.3, 7.4.7, 7.2.11, 7.0.13 or later versions. Coordinate a maintenance window for the update and validate SSO functionality post-patch.
FortiAnalyzer 7.0.14 or later (7.0.x branch); 7.2.11 or later (7.2.x branch); 7.4.7 or later (7.4.x branch); 7.6.3 or later (7.6.x branch)
- 1. Identify the current FortiAnalyzer version via CLI: `get system status` or via WebUI dashboard
- 2. Determine the appropriate upgrade path based on current version branch (7.0.x, 7.2.x, 7.4.x, or 7.6.x)
- 3. Back up the current FortiAnalyzer configuration via WebUI: System Settings > Maintenance > Backup & Restore, or via CLI: `execute backup config`
- 4. Download the appropriate firmware upgrade from Fortinet Customer Support portal: https://support.fortinet.com/
- 5. Upload and install the firmware via WebUI: System Settings > Firmware, or via CLI: `execute upgrade` with the firmware file
- 6. After upgrade completes, verify the fixed version is running: `get system status`
- 7. Verify the FortiCloud SSO functionality is working correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortianalyzer
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54973 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54973 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data