CVE-2025-53845VulnerabilityPublished 14 Oct 2025Updated 14 Jan 2026

CVE-2025-53845: Fortinet FortiAnalyzer · Improper access control

Affects Fortinet FortiAnalyzerSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L/E:P/RL:X/RC:C

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: Low

Temporal metrics

Exploit Code Maturity: Proof-of-Concept
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.
Exploit Code Maturity: Proof-of-Concept: Proof-of-concept exploit code is available, or an attack demonstration is not practical for most systems. The code or technique is not functional in all situations and may require substantial modification by a skilled attacker.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Fortinet FortiAnalyzer	Affected =7.6.0 =7.4.0 =7.2.0 =7.0.0 =6.4.0	Fixed in–

AI-suggested

European organizations should immediately assess their FortiAnalyzer deployments to identify affected versions (7.6.0 through 7.6.3 and versions before 7.4.6). Although no official patches are linked in the provided data, organizations should monitor Fortinet advisories closely and apply vendor-released patches or updates as soon as they become available. In the interim, network-level mitigations should be implemented: restrict access to FortiAnalyzer management interfaces and OFTP ports to trusted IP addresses only, ideally via firewall rules or network segmentation. Deploy intrusion detection/prevention systems (IDS/IPS) with signatures or anomaly detection for suspicious OFTP traffic patterns. Enable and review detailed logging on FortiAnalyzer to detect unusual access attempts or service disruptions. Consider disabling OFTP services if not required for operational needs. Conduct regular vulnerability scans and penetration tests focused on Fortinet devices to identify and remediate exposure. Finally, ensure incident response teams are aware of this vulnerability and prepared to respond to potential exploitation attempts.

Description

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.

Impact

For European organizations, the impact of CVE-2025-53845 can be substantial, particularly for those relying on FortiAnalyzer for centralized security monitoring and log management. Unauthorized access to device health and status information could provide attackers with insights into network topology, device configurations, and potential weaknesses, facilitating more targeted attacks. The ability to cause denial of service could disrupt security monitoring, delaying detection and response to other threats. This is especially critical for sectors with stringent regulatory requirements such as finance, healthcare, and critical infrastructure, where uninterrupted security operations are essential. The medium severity rating indicates that while the vulnerability is not catastrophic, it poses a meaningful risk that could degrade security posture and operational continuity. Given the lack of authentication required for exploitation, the attack surface is broad, increasing the likelihood of opportunistic attacks if unpatched. The absence of known exploits in the wild suggests a window of opportunity for proactive mitigation before widespread exploitation occurs.

References

fortiguard.fortinet.com/psirt/FG-IR-25-378 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jan 2026, 14:47 UTC

Technical details

References

Community reviews

Related threats