Fortinet FortiOS, FortiPAM, FortiProxy and FortiSwitchManager: logged-in admins can write or delete system files
A person who already has admin login on these Fortinet devices can abuse certain command-line commands to change or delete files they should not be able to reach. This can break the device or let them hide further changes.
| Severity | CriticalCVSS 6 of 10 |
|---|---|
| Being exploited? | YesConfirmed by CISA KEV · 16 Oct 2026 |
| Fix available? | UnclearNo fixed version published in the sources yet |
| How sure is this? | Official, 2 sourcesBacked by an official source |
How the attack works simplified
- 1Admin accountAttacker has valid admin login
- 2Crafted CLI commandUses path traversal sequences in input
- 3Escape directoryReaches paths outside allowed folder
- 4Write or delete filesAlters or removes arbitrary system files
- ResultDevice files tampered or destroyed
What happened
A path traversal flaw (CWE-22) in specific CLI commands lets an authenticated admin with at least read-write permissions write or delete arbitrary files on affected FortiOS, FortiPAM, FortiProxy and FortiSwitchManager releases.
Are you affected?
You are affected if you run FortiOS 7.6.0-7.6.4, 7.4.0-7.4.9, or any 7.2, 7.0 or 6.4 release; FortiPAM 1.0-1.7.0; FortiProxy 7.6.0-7.6.4, 7.4.0-7.4.11, or any 7.2 or 7.0 release; or FortiSwitchManager 7.2.0-7.2.7 or 7.0.0-7.0.6.
FortiOS 7.6.0-7.6.4; FortiOS 7.4.0-7.4.9; FortiOS 7.2 (all); FortiOS 7.0 (all); FortiOS 6.4 (all); FortiPAM 1.0-1.7.0 (all listed); FortiProxy 7.6.0-7.6.4; FortiProxy 7.4.0-7.4.11; FortiProxy 7.2 (all); FortiProxy 7.0 (all); FortiSwitchManager 7.2.0-7.2.7; FortiSwitchManager 7.0.0-7.0.6
What to do
- Check the Fortinet advisory for the fixed versions and apply the vendor update to every affected device.
- If no update is available yet, apply the vendor's mitigation and restrict administrative access to trusted management networks.
- Review admin accounts and remove unnecessary admin or read-write privileges.
- Follow CISA BOD 26-04 guidance and the Forensics Triage Requirements to check devices for signs of compromise, especially if internet-exposed.
Timeline
- 14 Apr 2026, 18:30 UTCPublicly disclosed
- 16 Oct 2026, 00:00 UTCReported by CISA KEV · CISA KEV
- 25 Oct 2026, 17:35 UTCGitHub Advisory reported on it · GitHub Advisory
Sources 2 reports, oldest first
Official vendor, government CERT or advisory database
- An Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') [CWE-22]...GitHub Advisory · 14 Apr 2026, 18:30 UTC
- CISA KEV16 Oct 2026, 00:00 UTC
Technical details
- ID
- CVE-2025-61624 · GHSA-f3vf-64gv-cxr8
- CVSS
- 6 / 10
- EPSS
- 1.3% chance of exploitation within 30 days
- Disclosed
- 14 Apr 2026, 18:30 UTC
- On Zero Radar
- before the radar started
- Last change
- 25 Oct 2026, 17:35 UTC
The plain-language parts and the attack diagram were written by an AI model (anthropic/claude-haiku-5.5) from the sources above. Facts like versions, exploitation and dates come from the sources themselves. How Zero Radar works