CyberSecBulletin
CVE-2025-61624Exploited in the wildNVD status: Analyzed

Fortinet Multiple Products Path Traversal

Published Updated By the CyberSecBulletin desk

CVE-2025-61624 is a medium-severity improper limitation of a pathname to a restricted directory vulnerability in FortiOS from Fortinet, with a CVSS 3.1 base score of 6.5 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. Affected FortiOS versions: 7.6.0 through 7.6.4; 7.4.0 through 7.4.9; 7.2.0 through 7.2.13, and others listed below. The record does not name a fixed version, so check the vendor advisory. CISA added it to the Known Exploited Vulnerabilities catalogue on October 16, 2026, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Check which version of FortiOS you run against the affected versions below, and install the vendor's latest release.
  2. CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
  3. Read the advisory on fortiguard.fortinet.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
FortinetFortiOS7.6.0 through 7.6.4; 7.4.0 through 7.4.9; 7.2.0 through 7.2.13; 7.0.0 through 7.0.19; 6.4.0 through 6.4.16Not stated
FortinetFortiProxy7.6.0 through 7.6.4; 7.4.0 through 7.4.11; 7.2.0 through 7.2.16; 7.0.0 through 7.0.23Not stated
FortinetFortiSwitchManager7.2.0 through 7.2.7; 7.0.0 through 7.0.6Not stated
FortinetFortiPAM1.7.0; 1.6.0 through 1.6.2; 1.5.0 through 1.5.1; 1.4.0 through 1.4.3; 1.3.0 through 1.3.1; 1.2.0; 1.1.0 through 1.1.2; 1.0.0 through 1.0.3Not stated
SiemensRUGGEDCOM APE1808all versionsNot stated
SiemensRuggedcom Ape1808 FirmwareNot specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
HighAdministrator-level access is required first.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.16.0MediumCNA (fortinet.com)
CVSS 3.16.5MediumNVD

Official description

An Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') [CWE-22] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.4, FortiOS 7.4.0 through 7.4.9, FortiOS 7.2 all versions, FortiOS 7.0 all versions, FortiOS 6.4 all versions, FortiPAM 1.7.0, FortiPAM 1.6 all versions, FortiPAM 1.5 all versions, FortiPAM 1.4 all versions, FortiPAM 1.3 all versions, FortiPAM 1.2 all versions, FortiPAM 1.1 all versions, FortiPAM 1.0 all versions, FortiProxy 7.6.0 through 7.6.4, FortiProxy 7.4.0 through 7.4.11, FortiProxy 7.2 all versions, FortiProxy 7.0 all versions, FortiSwitchManager 7.2.0 through 7.2.7, FortiSwitchManager 7.0.0 through 7.0.6 may allow an authenticated attacker with admin profile and at least read-write permissions to write or delete arbitrary files via specific CLI commands.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

How developers prevent this class of flaw

  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.

More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
  3. Added to CISA's Known Exploited Vulnerabilities catalogue.
  4. Record last changed materially (score, affected products, status or references).
  5. Deadline for US federal agencies to remediate, set by CISA.

References

Other vulnerabilities in FortiOS

All FortiOS vulnerabilities

Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities

Spotted an error? Tell us.