A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet Fo…
- Severity
- Critical9.1CVSS 3.1, Critical
- EPSS
- 15%
- Published
- 14 Jan 2025
- Updated
- 8 Jul 2026
Description
Title, description and vendor guidance are quoted from the source records.
A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiManager 7.6.0 through 7.6.1, FortiManager 7.4.1 through 7.4.3, FortiManager Cloud 7.4.1 through 7.4.3, FortiOS 7.6.0, FortiOS 7.4.0 through 7.4.4, FortiOS 7.2.0 through 7.2.9, FortiOS 7.0.0 through 7.0.15, FortiOS 6.4.0 through 6.4.15, FortiProxy 7.4.0 through 7.4.5, FortiProxy 7.2.0 through 7.2.11, FortiProxy 7.0.0 through 7.0.18, FortiProxy 2.0 all versions, FortiProxy 1.2 all versions, FortiProxy 1.1 all versions, FortiProxy 1.0 all versions may allow a remote authenticated attacker with access to the security fabric interface and port to write arbitrary files or a remote unauthenticated attacker to delete an arbitrary folder
Weakness: CWE-22
Known exploited
Not listed in CISA KEV as of the last check.
Exploit prediction
15% probability of exploitation in the next 30 days (percentile 97%).
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
What the source states, per branch
Versions matched by Patcharo
Fortinet FortiManagerSource: Fortinet (CVE record)
| Branch | Affected | Fixed in |
|---|---|---|
| 7.6 | 7.6.0 – 7.6.1 | Fixed after 7.6.1 |
| 7.4 | 7.4.1 – 7.4.3 | Fixed after 7.4.3 |
Versions not listed are stated unaffected by the vendor.
Fortinet FortiProxySource: Fortinet (CVE record)
| Branch | Affected | Fixed in |
|---|---|---|
| 7.4 | 7.4.0 – 7.4.5 | Fixed after 7.4.5 |
| 7.2 | 7.2.0 – 7.2.11 | Fixed after 7.2.11 |
| 7.0 | 7.0.0 – 7.0.18 | Fixed after 7.0.18 |
| 2.0 | 2.0.0 – 2.0.14 | Fixed after 2.0.14 |
| 1.2 | 1.2.0 – 1.2.13 | Fixed after 1.2.13 |
| 1.1 | 1.1.0 – 1.1.6 | Fixed after 1.1.6 |
| 1.0 | 1.0.0 – 1.0.7 | Fixed after 1.0.7 |
Versions not listed are stated unaffected by the vendor.
Fortinet FortiOSSource: Fortinet (CVE record)
| Branch | Affected | Fixed in |
|---|---|---|
| 7.6 | Exact releases: 7.6.0 | |
| 7.4 | 7.4.0 – 7.4.4 | Fixed after 7.4.4 |
| 7.2 | 7.2.0 – 7.2.9 | Fixed after 7.2.9 |
| 7.0 | 7.0.0 – 7.0.15 | Fixed after 7.0.15 |
| 6.4 | 6.4.0 – 6.4.15 | Fixed after 6.4.15 |
Versions not listed are stated unaffected by the vendor.
Affected products
- Fortinet FortiManager Cloud · 7.4.1 ≤ 7.4.3
Workaround / Vendor remediation
Vendor remediation · FortiManager
Upgrade to upcoming FortiAuthenticator version 7.0.0 or above Upgrade to FortiOS version 7.6.1 or above Upgrade to FortiOS version 7.4.5 or above Upgrade to FortiOS version 7.2.10 or above Upgrade to FortiOS version 7.0.16 or above Upgrade to FortiOS version 6.4.16 or above Upgrade to FortiWeb version 7.6.1 or above Upgrade to FortiWeb version 7.4.5 or above Upgrade to FortiRecorder version 7.2.2 or above Upgrade to FortiRecorder version 7.0.5 or above Upgrade to FortiManager Cloud version 7.4.4 or above Upgrade to FortiProxy version 7.4.6 or above Upgrade to FortiProxy version 7.2.12 or above Upgrade to FortiProxy version 7.0.19 or above Upgrade to FortiVoice version 7.2.0 or above Upgrade to FortiVoice version 7.0.5 or above Upgrade to FortiVoice version 6.4.10 or above Fortinet remediated this issue in FortiSASE version 24.3.c and hence customers do not need to perform any action. Up…
Vendor remediation · FortiProxy
Upgrade to upcoming FortiAuthenticator version 7.0.0 or above Upgrade to FortiOS version 7.6.1 or above Upgrade to FortiOS version 7.4.5 or above Upgrade to FortiOS version 7.2.10 or above Upgrade to FortiOS version 7.0.16 or above Upgrade to FortiOS version 6.4.16 or above Upgrade to FortiWeb version 7.6.1 or above Upgrade to FortiWeb version 7.4.5 or above Upgrade to FortiRecorder version 7.2.2 or above Upgrade to FortiRecorder version 7.0.5 or above Upgrade to FortiManager Cloud version 7.4.4 or above Upgrade to FortiProxy version 7.4.6 or above Upgrade to FortiProxy version 7.2.12 or above Upgrade to FortiProxy version 7.0.19 or above Upgrade to FortiVoice version 7.2.0 or above Upgrade to FortiVoice version 7.0.5 or above Upgrade to FortiVoice version 6.4.10 or above Fortinet remediated this issue in FortiSASE version 24.3.c and hence customers do not need to perform any action. Up…
Vendor remediation · FortiOS
Upgrade to upcoming FortiAuthenticator version 7.0.0 or above Upgrade to FortiOS version 7.6.1 or above Upgrade to FortiOS version 7.4.5 or above Upgrade to FortiOS version 7.2.10 or above Upgrade to FortiOS version 7.0.16 or above Upgrade to FortiOS version 6.4.16 or above Upgrade to FortiWeb version 7.6.1 or above Upgrade to FortiWeb version 7.4.5 or above Upgrade to FortiRecorder version 7.2.2 or above Upgrade to FortiRecorder version 7.0.5 or above Upgrade to FortiManager Cloud version 7.4.4 or above Upgrade to FortiProxy version 7.4.6 or above Upgrade to FortiProxy version 7.2.12 or above Upgrade to FortiProxy version 7.0.19 or above Upgrade to FortiVoice version 7.2.0 or above Upgrade to FortiVoice version 7.0.5 or above Upgrade to FortiVoice version 6.4.10 or above Fortinet remediated this issue in FortiSASE version 24.3.c and hence customers do not need to perform any action. Up…
References
Provenance
Every fact on this page comes from the sources below. Nothing is written by an AI.
- Fortinet (CVE record)
- Fortinet (CVE record) · 27 Sept 2026, 23:46 UTC · Parser patcharo-cve5/1.1.0
- NVD
- NVD · 27 Sept 2026, 23:44 UTC · Parser patcharo-nvd/1.0.0
- FIRST EPSS
- FIRST EPSS · 27 Sept 2026, 23:46 UTC · Parser patcharo-epss/1.0.0
Last verified: 28 Sept 2026, 02:31 UTC