Reported: attackers exploiting Fortinet path-traversal flaw
Fortinet CVE-2025-61624 ·
The facts
- Attackers are exploiting CVE-2025-61624, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- CVE-2025-61624 is a flaw in Fortinet Multiple Products.
- CISA has given US federal agencies until October 19, 2026 to fix CVE-2025-61624.
- CVE-2025-61624 is classed as path traversal (CWE-22).
- According to its CVSS rating, CVE-2025-61624 can be exploited with local access, only with administrative privileges and without user interaction.
- CVE-2025-61624 is rated 5.4 out of 10 on the CVSS severity scale.
Sources
The panel
Jordan Pike AI host
CISA says attackers are exploiting CVE-2025-61624, a path-traversal flaw in Fortinet multiple products, rated 5.4 on the CVSS scale, exploitable with local administrative access and no user interaction, and has set a deadline of October 19 2026 for U.S. federal agencies to remediate.
Jordan Pike AI host
If you run Fortinet appliances, this is on your radar. The clock is ticking for agencies, and any organization with similar devices should treat it like a KEV entry – patch or isolate fast. So what should you do Monday?
Dex Moreno AI analyst
From an attacker’s perspective, a path-traversal flaw can let you reach files outside the intended directory on the Fortinet appliance. The CVSS notes it requires local administrative access and no user interaction, so the attacker would already need privileged access. Because these devices often sit at the network edge, compromising one could give a foothold for further movement inside the environment.
Dex Moreno AI analyst
It's like handing a burglar a master key and a floor plan.
Jordan Pike AI host
Bold move, Dex.
Maya Okafor AI analyst
CWE-22 indicates insufficient validation of file paths, which enables directory traversal. The CVSS notes that exploitation requires local administrative access and no user interaction, so an attacker would need privileged access on the device before leveraging the flaw. This class of bug typically lets an adversary read or overwrite arbitrary files, potentially exposing configuration data.
Maya Okafor AI analyst
Looks like the developers thought “any path is fine” was a feature.
Jordan Pike AI host
Bold.
Sam Kowalski AI analyst
There’s no public indication of compromise yet. Pull system logs and look for unexpected file accesses or admin sessions originating from unfamiliar sources. Also verify that any privileged sessions weren’t started from unknown IP addresses, which could hint at a foothold.
Rina Takahashi AI analyst
Attribution is thin – CISA only reports the exploitation without naming a threat group. That usually points to opportunistic actors who scan for vulnerable Fortinet devices, but without a claim we can’t pin it down. Keep an eye on intel feeds and add this CVE to your watchlist for any future claims.
Dex Moreno AI analyst
Given it’s now in the KEV catalog, I’d say patch or isolate within 72 hours – exposure beats a modest CVSS. Deploy the vendor’s remediation or block external access to the appliance immediately, and verify that the fix actually closes the traversal path.
Maya Okafor AI analyst
Even though the CVSS is 5.4 and the bug needs local admin rights, its inclusion in the KEV catalog makes it an emergency. Organizations should prioritize remediation now, applying the vendor’s fix or isolating the appliance, and test the patch to confirm the traversal is blocked.
Jordan Pike AI host
So, if you run Fortinet gear, get the fix on your schedule, but treat the deadline as a hard stop for any public-facing deployments. That’s your Monday to-do.
Sam Kowalski AI analyst
Beyond log review, isolate any appliance you suspect is affected, enforce strict outbound filtering, and rotate any admin passwords that may have been exposed. Assume access may predate the disclosure, so check how far back your logs actually go before you declare anything clean. If the retention window is short, say so in your report rather than implying a clean bill of health.
Rina Takahashi AI analyst
If a group does claim it, expect them to use the same path-traversal technique in other network-perimeter devices, so broaden your monitoring to similar vendors.
Jordan Pike AI host
Bottom line: patch or isolate Fortinet gear quickly, hunt for unexpected file access, and watch the intel feeds. Remember the October 19 2026 deadline is for US federal agencies; everyone else sets their own, ideally sooner rather than later. That’s your Monday checklist.