# CVE-2025-61624: Fortinet Multiple Products Path Traversal

> Authenticated administrators can write or delete arbitrary files on Fortinet network devices via path traversal in CLI commands.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 16 Oct 2026 (CISA KEV)
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2026
- **Updated:** 17 Oct 2026
- **Also known as:** GHSA-f3vf-64gv-cxr8

## What is CVE-2025-61624?

CVE-2025-61624 is a medium-severity path traversal vulnerability in Fortinet Fortios, published on 14 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-61624?

It affects 5 products.


Products: Fortinet Fortios, Fortinet Fortipam, Fortinet Fortiproxy, Fortinet Fortiswitchmanager, Siemens Ruggedcom Ape1808 Firmware.

## How do I fix CVE-2025-61624?

No fix has been published for CVE-2025-61624 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 19 Oct 2026.

## Is CVE-2025-61624 being exploited?

Yes. Attackers have exploited CVE-2025-61624 in the wild since at least 16 Oct 2026.

## Other vulnerabilities in Fortinet Fortios

- [CVE-2024-23113](https://insights.sbomify.com/CVE-2024-23113/): Fortinet Multiple Products Format String (critical 9.8, exploited in the wild)
- [CVE-2022-40684](https://insights.sbomify.com/CVE-2022-40684/): Fortinet Multiple Products Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2024-55591](https://insights.sbomify.com/CVE-2024-55591/): Fortinet FortiOS and FortiProxy Authentication Bypass (critical 9.6, exploited in the wild)
- [CVE-2024-21762](https://insights.sbomify.com/CVE-2024-21762/): Fortinet FortiOS Out-of-Bound Write (critical 9.6, exploited in the wild)
- [CVE-2022-42475](https://insights.sbomify.com/CVE-2022-42475/): Fortinet FortiOS Heap-Based Buffer Overflow (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61624 and fix it if it is affected.

What it is: CVE-2025-61624 is a medium-severity path traversal vulnerability in Fortinet Fortios, published on 14 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-61624 in the wild since at least 16 Oct 2026.

Affected product: Fortinet Fortios. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-61624/ (Markdown: https://insights.sbomify.com/CVE-2025-61624/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-61624
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-61624
- OSV: https://osv.dev/vulnerability/CVE-2025-61624

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-61624/
Summaries are generated and may contain mistakes; the official description above is the record.