dbcve.org
FortianalyzerApplication · Fortinet

CVE-2025-67604

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 7.4.9 / 7.6.5 or later.
See remediation →
59/100
Remediation priority · Elevated
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 potentially dangerous function vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.4, FortiAnalyzer 7.4.0 through 7.4.8, FortiAnalyzer 7.2 all versions, FortiAnalyzer 7.0 all versions, FortiAnalyzer 6.4 all versions, FortiManager 7.6.0 through 7.6.4, FortiManager 7.4.0 through 7.4.8, FortiManager 7.2 all versions, FortiManager 7.0 all versions, FortiManager 6.4 all versions may allow an authenticated attacker to cause a system hang via multiple specially crafted HTTP requests causing crashes. This happens if internal locks are aligned, which is out of control of the attacker.

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 · moderate confidence

A use of potentially dangerous function vulnerability in FortiAnalyzer and FortiManager allows authenticated attackers to cause system hang/crashes via specially crafted HTTP requests. The crash occurs when internal locks become aligned, though this lock alignment condition is noted as out of the attacker's control, suggesting unreliable exploitation.

MitigationApply the vendor patch for FortiAnalyzer and FortiManager to address the affected versions. Since authentication is required, ensure least-privilege access controls and monitor for anomalous HTTP traffic patterns.

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.2.0, <= 7.2.12>= 7.4.0, < 7.4.9>= 7.6.0, < 7.6.5
FortimanagerApplication
Affected:>= 7.2.0, <= 7.2.12>= 7.4.0, < 7.4.9>= 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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/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. Check FortiAnalyzer version
    Run command: get system status or fnsysctl get system status on the FortiAnalyzer CLI
    Affected if The version falls within 7.2.0-7.2.12, 7.4.0-7.4.8, or 7.6.0-7.6.4
  2. Check FortiManager version
    Run command: get system status or fnsysctl get system status on the FortiManager CLI
    Affected if The version falls within 7.2.0-7.2.12, 7.4.0-7.4.8, or 7.6.0-7.6.4
  3. Verify HTTP service is enabled
    Check admin interface accessibility via GUI or CLI: get system interface or show system interface in CLI
    Affected if The web administration interface is exposed and reachable from network segments where attackers could send HTTP requests
  4. Identify authentication method in use
    Review admin user configuration: get admin user or show system admin in CLI
    Affected if The system allows authenticated attacker access, meaning any admin-level account could trigger the vulnerable code path with crafted HTTP requests
  5. Check for crash logs or system hang events
    Review system logs: execute log filter category 2; execute diag crashlog show or check /var/log/gui_event.log
    Affected if Recent crash logs or system hang events correlate with HTTP request activity from admin accounts

A system is affected if it runs a vulnerable FortiAnalyzer or FortiManager version (7.2.0-7.2.12, 7.4.0-7.4.8, or 7.6.0-7.6.4) with the HTTP admin interface accessible to authenticated users who could send specially crafted requests.

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

Apply the vendor patch for FortiAnalyzer and FortiManager to address the affected versions. Since authentication is required, ensure least-privilege access controls and monitor for anomalous HTTP traffic patterns.

Recommended fix High confidence

FortiAnalyzer/FortiManager 7.2.13+, 7.4.9+, or 7.6.5+ (depending on your major version branch)

  1. 1. Identify the current FortiAnalyzer and/or FortiManager version running in your environment
  2. 2. For FortiAnalyzer 7.2.x: Upgrade to version 7.2.13 or later
  3. 3. For FortiAnalyzer 7.4.x: Upgrade to version 7.4.9 or later
  4. 4. For FortiAnalyzer 7.6.x: Upgrade to version 7.6.5 or later
  5. 5. For FortiManager 7.2.x: Upgrade to version 7.2.13 or later
  6. 6. For FortiManager 7.4.x: Upgrade to version 7.4.9 or later
  7. 7. For FortiManager 7.6.x: Upgrade to version 7.6.5 or later
  8. 8. Verify the upgrade was successful and the system is operational
Caveat Review Fortinet release notes for your version branch for any configuration or behavioral changes before upgrading

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

Fix this in Fortianalyzer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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