dbcve.org
FortianalyzerApplication · Fortinet

CVE-2025-53845

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 7.4.7 / 7.6.4 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
An improper authentication vulnerability [CWE-287] in Fortinet FortiAnalyzer version 7.6.0 through 7.6.3 and before 7.4.6 allows an unauthenticated attacker to obtain information pertaining to the device's health and status, or cause a denial of service via crafted OFTP 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 confidence

FortiAnalyzer versions 7.6.0 through 7.6.3 and versions before 7.4.6 contain an improper authentication vulnerability in the OFTP (Optimized Fabric Transfer Protocol) service. Attackers can send specially crafted OFTP requests without authentication to retrieve sensitive device health and status information or trigger a denial of service condition.

MitigationUpgrade FortiAnalyzer to version 7.4.6 or later (for 7.4.x branch) or version 7.6.4 or later (for 7.6.x branch). If immediate patching is not possible, restrict network access to OFTP ports and monitor for anomalous OFTP traffic.

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
Affected:>= 6.4.0, < 7.4.7>= 7.6.0, < 7.6.4

CVSS 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FortiAnalyzer installed version
    Run 'get system status' in FortiAnalyzer CLI or view in web UI under Dashboard > System Information widget
    Affected if Version is 7.6.0-7.6.3 or 7.4.0-7.4.6 or any 6.4.x version (falling within >=6.4.0,<7.4.7 or >=7.6.0,<7.6.4)
  2. Verify OFTP service is configured
    Run 'get system onetp' in CLI to view OFTP configuration settings
    Affected if OFTP is enabled and configured on the device (the vulnerability only applies when OFTP service is active)
  3. Check OFTP service status
    Run 'diagnose test application onetp 3' in CLI to display OFTP daemon status and connection info
    Affected if OFTP daemon is running and listening on ports (default 514 UDP for syslog-like OFTP traffic)

You are affected if your FortiAnalyzer version falls within the vulnerable ranges AND OFTP service is enabled, since the flaw allows unauthenticated OFTP requests to retrieve sensitive information or cause denial of service.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.4.7 / 7.6.4 or later
Fixed in 7.4.77.6.4
Interim mitigation

Upgrade FortiAnalyzer to version 7.4.6 or later (for 7.4.x branch) or version 7.6.4 or later (for 7.6.x branch). If immediate patching is not possible, restrict network access to OFTP ports and monitor for anomalous OFTP traffic.

Recommended fix High confidence

FortiAnalyzer 7.4.7 or later (7.4.x branch), or 7.6.4 or later (7.6.x branch)

  1. 1. Identify the current FortiAnalyzer version by running: `get system status` in the FortiAnalyzer CLI or checking in the web UI under System Settings > Dashboard > Status
  2. 2. If running version 7.4.x (versions before 7.4.7), plan an upgrade to version 7.4.7 or later in the 7.4.x branch
  3. 3. If running version 7.6.0 through 7.6.3, plan an upgrade to version 7.6.4 or later in the 7.6.x branch
  4. 4. Before upgrading, backup the FortiAnalyzer configuration via: `execute backup all-settings` in the CLI
  5. 5. Download the appropriate firmware from Fortinet Customer Support portal (https://support.fortinet.com)
  6. 6. Upload the firmware via the web UI under System Settings > Firmware or via the CLI: `execute restore image <tftp/ftp> <filename>`
  7. 7. Reboot the device after firmware installation completes
  8. 8. Verify the upgrade was successful and the version is now at 7.4.7+ or 7.6.4+ using: `get system status`
Caveat Review Fortinet release notes for the target version for any configuration or feature changes that may affect existing setups; test in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortianalyzer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53845 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-53845 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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