CVE Intelligence
Medium

CVE-2025-67604 — A use of potentially dangerous function vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6...

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.

Published May 12, 2026 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: fortinet

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.4% (30-day exploitation probability)+5
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.42%
ahead of 35% of scored CVEs · Oct 14, 2026
Affects
Fortinet
Fortianalyzer and 1 more
CVSS base
5.3
Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Fortinet Fortianalyzer, Fortinet Fortimanager).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Fortinet Fortianalyzer ≥ 7.2.0 and ≤ 7.2.12≥ 7.4.0 and < 7.4.9≥ 7.6.0 and < 7.6.5 Vulnerable NIST National Vulnerability Database
Fortinet Fortianalyzer ≥ 7.6.0 and ≤ 7.6.4≥ 7.4.0 and ≤ 7.4.8≥ 7.2.0 and ≤ 7.2.12≥ 7.0.0 and ≤ 7.0.16≥ 6.4.0 and ≤ 6.4.15 Vulnerable CVE Program (cve.org) e CISA ADP
Fortinet Fortimanager ≥ 7.2.0 and ≤ 7.2.12≥ 7.4.0 and < 7.4.9≥ 7.6.0 and < 7.6.5 Vulnerable NIST National Vulnerability Database
Fortinet Fortimanager ≥ 7.6.0 and ≤ 7.6.4≥ 7.4.0 and ≤ 7.4.8≥ 7.2.0 and ≤ 7.2.12≥ 7.0.0 and ≤ 7.0.16≥ 6.4.0 and ≤ 6.4.15 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.3 CVSS 3.1 Medium 1.6 3.6 psirt@fortinet.com via NIST National Vulnerability Database
5.3 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
5.2 CVSS 3.1 Medium — — fortinet via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: psirt@fortinet.com)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 5.3 (psirt@fortinet.com via NIST National Vulnerability Database) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-676

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.42%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · fortinet/fortianalyzer, fortinet/fortimanager
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 5.3
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    May 12, 2026 · fortinet

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

3 on the record

Elsewhere on this site

Fortinet
every CVE for this vendor
CWE-676
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-23705 An Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')... 2d
  • CVE-2026-23707 An Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')... 2d
  • CVE-2026-23706 An Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')... 2d
  • CVE-2026-106171 A improper neutralization of special elements used in an os command ('os command injection')... 2d
  • CVE-2025-46773 An Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')... 2d
  • CVE-2025-68649 An improper limitation of a pathname to a restricted directory ('path traversal') vulnerability... Apr 14, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-67604 is "A use of potentially dangerous function vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6...", rated Medium. It affects Fortianalyzer (Fortinet); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. EPSS 0.42% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.