Skip to content
vulnerability

CVE-2025-61624

6.0
Medium
KEV · Exploited in wildEPSS 1%Patch available

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.

exploited
Yes, in CISA KEV since 16 Oct 2026fix by 19 Oct 2026 (CISA deadline for US federal agencies)
fix
Patch available see the advisory in the references
likelihood
EPSS 1.3%
Published 14 Apr 2026Analysed here 2 Nov 2026

do firstApply 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.

triage
server-sideruntimeWAF can block: noAV · localCWE-22· Path Traversal

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: canonical path validation

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectorlocalattack complexitylowprivileges requiredhighuser interactionnonescopeunchangedconfidentialitynoneintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
common questions

Is CVE-2025-61624 being exploited?

Yes. CVE-2025-61624 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-61624?

CVE-2025-61624 is rated Medium with a CVSS score of 6.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-61624?

Yes. A fix has been recorded for CVE-2025-61624. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-61624 affect?

CVE-2025-61624 affects fortinet:fortios, fortinet:fortipam, fortinet:fortiproxy, fortinet:fortiswitchmanager, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
fortinet:fortiosfortinet:fortipamfortinet:fortiproxyfortinet:fortiswitchmanagersiemens:ruggedcom_ape1808_firmware
affected versions
Fortinet FortiOS
  • affected>= 7.6.0 and <= 7.6.4
  • affected>= 7.4.0 and <= 7.4.9
  • affected>= 7.2.0 and <= 7.2.13
  • affected>= 7.0.0 and <= 7.0.19
  • affected>= 6.4.0 and <= 6.4.16
Fortinet FortiPAM
  • affected1.7.0
  • affected>= 1.6.0 and <= 1.6.2
  • affected>= 1.5.0 and <= 1.5.1
  • affected>= 1.4.0 and <= 1.4.3
  • affected>= 1.3.0 and <= 1.3.1
  • affected1.2.0
  • affected>= 1.1.0 and <= 1.1.2
  • affected>= 1.0.0 and <= 1.0.3
Fortinet FortiProxy
  • affected>= 7.6.0 and <= 7.6.4
  • affected>= 7.4.0 and <= 7.4.11
  • affected>= 7.2.0 and <= 7.2.16
  • affected>= 7.0.0 and <= 7.0.23
Fortinet FortiSwitchManager
  • affected>= 7.2.0 and <= 7.2.7
  • affected>= 7.0.0 and <= 7.0.6

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 15 Oct 2026 (SSVC 2.0.3).

timeline

  1. 14 Apr 2026Published
  2. 15 Oct 2026CISA SSVC assessment: exploitation active · 183 days (about 6 months) later
  3. 16 Oct 2026Added to CISA KEV (exploited in the wild) · 1 day later
  4. 17 Oct 2026CVE record last updated · 1 day later
  5. 19 Oct 2026CISA remediation due date (US federal agencies) · 2 days later
  6. 2 Nov 2026Analysed by vulneraibility.com · 15 days later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
4 references in the CVE record: 1 advisory, 3 links

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved