dbcve.org
FortianalyzerApplication · Fortinet

CVE-2025-68648

HIGH · 7.2 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 7.4.8 / 7.6.5 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
A use of externally-controlled format string vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.4, FortiAnalyzer 7.4.0 through 7.4.7, FortiAnalyzer 7.2 all versions, FortiAnalyzer 7.0 all versions, FortiAnalyzer Cloud 7.6.2, FortiAnalyzer Cloud 7.4.1 through 7.4.7, FortiAnalyzer Cloud 7.2 all versions, FortiAnalyzer Cloud 7.0 all versions, FortiManager 7.6.0 through 7.6.4, FortiManager 7.4.0 through 7.4.7, FortiManager 7.2 all versions, FortiManager 7.0 all versions, FortiManager Cloud 7.6.2 through 7.6.3, FortiManager Cloud 7.4.1 through 7.4.7, FortiManager Cloud 7.2.1 through 7.2.10, FortiManager Cloud 7.0.1 through 7.0.14 may allow an attacker to escalate its privileges via specially crafted 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

A format string vulnerability exists in FortiAnalyzer and FortiManager where user-supplied input is used as a format string in certain functions. This can allow attackers to read from or write to memory locations, potentially leading to privilege escalation through specially crafted HTTP requests.

MitigationApply Fortinet's patches by upgrading to the fixed versions: FortiAnalyzer 7.6.5+, 7.4.8+, or later; FortiManager 7.6.5+, 7.4.8+, or later; and corresponding Cloud versions.

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:>= 7.0.0, < 7.4.8>= 7.6.0, < 7.6.5
Fortianalyzer CloudApplication
Affected:>= 7.0.0, < 7.4.8>= 7.6.0, < 7.6.5
FortimanagerApplication
Affected:>= 7.0.0, < 7.4.8>= 7.6.0, < 7.6.5
Fortimanager CloudApplication
Affected:>= 7.0.0, < 7.4.8>= 7.6.0, < 7.6.5

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

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

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 the installed Fortinet product
    Access the FortiAnalyzer or FortiManager web UI, or run 'get system status' via CLI to confirm the product name
    Affected if Product is FortiAnalyzer or FortiManager (or their Cloud variants)
  2. Determine the installed software version
    In web UI: go to System > Settings > About. In CLI: run 'get system status' and locate the 'FortiAnalyzer version' or 'FortiManager version' line
    Affected if Version cannot be determined or is below 7.4.8 or between 7.6.0-7.6.5
  3. Compare version against affected ranges
    Check if the version falls within: 7.0.0 <= version < 7.4.8 OR 7.6.0 <= version < 7.6.5
    Affected if Version matches either of these ranges (7.0.0-7.4.7 or 7.6.0-7.6.4)
  4. Verify remote access is enabled
    Confirm the web UI or API interface is accessible remotely (check 'config system interface' in CLI for HTTP/HTTPS listen ports)
    Affected if HTTP/HTTPS management interface is exposed and version is in affected range

You are affected if FortiAnalyzer or FortiManager (or Cloud variants) is running version 7.0.0-7.4.7 or 7.6.0-7.6.4 and the management interface is accessible.

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.8 / 7.6.5 or later
Fixed in 7.4.87.6.5
Interim mitigation

Apply Fortinet's patches by upgrading to the fixed versions: FortiAnalyzer 7.6.5+, 7.4.8+, or later; FortiManager 7.6.5+, 7.4.8+, or later; and corresponding Cloud versions.

Recommended fix High confidence

FortiAnalyzer/FortiManager 7.4.8+ or 7.6.5+

  1. 1. Identify the currently installed FortiAnalyzer or FortiManager version using the CLI command: get system status
  2. 2. For FortiAnalyzer/FortiManager 7.4.x versions (7.4.0-7.4.7), upgrade to version 7.4.8 or later
  3. 3. For FortiAnalyzer/FortiManager 7.6.x versions (7.6.0-7.6.4), upgrade to version 7.6.5 or later
  4. 4. For versions 7.0.x and 7.2.x, upgrade to the minimum fixed version in the 7.4.x or 7.6.x branch (7.4.8 or 7.6.5 respectively)
  5. 5. Download the firmware from the Fortinet Customer Support Portal: https://support.fortinet.com/
  6. 6. Upload and install the firmware via the FortiAnalyzer/FortiManager GUI (System > Firmware) or CLI: execute firmware upgrade <firmware_file>
  7. 7. After upgrade, verify the version: get system status and confirm the fix is applied
Caveat Review Fortinet release notes for the target version for any configuration or feature changes before upgrading; test in 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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68648 — 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-68648 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