SecOps SignalSecurity Intelligence Workspace
Collection Degraded30 / 46 Sources HealthyPublic Intel Only
Vulnerabilities/CVE-2025-61624Public Intelligence Dossier
Source: fortinet · Limited verification•Last verified: •Collection Degraded
CVE-2025-61624ListedMEDIUM (raw)CVSS 6.5CWE-22

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.

Published: 14 Apr 2026•Last updated: 17 Oct 2026, 12:41 AM IST•Source identifier: psirt@fortinet.com
Dossier completeness: source-provided sections 3 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Listed
Added16 Oct 2026
Due19 Oct 2026
RansomwareUnknown
CVSS score
6.5MEDIUM (raw)
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
Metric sourcenvd@nist.gov
EPSS probability
0.6%0.006
Percentile47th
Weakness type
CWE-22
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

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.

SOC priority

Immediate Attention

Actively exploited

Yes

Publicly disclosed

Unknown

Risk basis: CISA KEV exploitation signal; SOC ecosystem technology relevance; Known exploitation signal from CISA KEV or ransomware metadata

Affected Products & Remediation

5 source-backed products
Affected products and versions (source)
  • fortinet fortios · >= 6.4.0 < 7.4.10; >= 7.6.0 < 7.6.5 · NVD CPE · Source
  • fortinet fortipam · >= 1.0.0 < 1.7.1 · NVD CPE · Source
  • fortinet fortiproxy · >= 7.0.0 < 7.4.12; >= 7.6.0 < 7.6.5 · NVD CPE · Source
  • fortinet fortiswitchmanager · >= 7.0.0 < 7.0.7; >= 7.2.0 < 7.2.8 · NVD CPE · Source
  • siemens ruggedcom ape1808 firmware · version range not provided by source · NVD CPE · Source
NVD applicability prerequisites: cpe:2.3:h:siemens:ruggedcom_ape1808:-:*:*:*:*:*:*:*. These are conditions, not proof that an environment is exposed or unaffected.
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

  • CISA KEV: Apply 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.

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Listed
Exploited (source statement)
Yes
Publicly disclosed (source)
Unknown

CISA required action: Apply 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.

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched kev-network-exposure (CVSS AV:N, CISA KEV Listed); path-traversal (CWE-22)

Exposure

  1. Identify assets with the exact CVE and confirm the affected product/version against the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · KEV listing raises urgency, but inventory is needed to establish local exposure. · Rule kev-network-exposure
  2. Locate affected deployments and the path-handling endpoint named by the advisory.Telemetry: Application access logs · The affected path must come from the source, not the CWE alone. · Rule path-traversal

Exploitation evidence

  1. Review relevant edge or application access logs for unusual requests around the advisory window.Telemetry: CommonSecurityLog · Log review is a hunting hypothesis; KEV listing alone does not show local exploitation. · Rule kev-network-exposure
Show more (2)

Exploitation evidence

  1. Review requests to that endpoint for traversal encodings and unusual file responses.Telemetry: Application access logs · Such patterns are a hypothesis to validate against normal traffic. · Rule path-traversal

Response

  1. Recheck the affected assets after the source-stated mitigation or update is applied.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies local remediation. · Rule kev-network-exposure

CISA KEV Record

Catalog entry
16 Oct 2026
Required action due
19 Oct 2026
Known ransomware use
Unknown

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

Change History & Source Data

— No recorded material change

CNA / source
psirt@fortinet.com
Record status · verification
UPDATED · CISA KEV confirmed
CPE
cpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:*, cpe:2.3:o:fortinet:fortipam:*:*:*:*:*:*:*:*, cpe:2.3:a:fortinet:fortiproxy:*:*:*:*:*:*:*:*, cpe:2.3:a:fortinet:fortiswitchmanager:*:*:*:*:*:*:*:*, cpe:2.3:o:siemens:ruggedcom_ape1808_firmware:-:*:*:*:*:*:*:*, cpe:2.3:h:siemens:ruggedcom_ape1808:-:*:*:*:*:*:*:*

Evidence & Provenance

4 public sources
CISA KEV CatalogAdded 2026-10-16fortiguard.fortinet.comSource recordnvd.nist.govSource recordcert-portal.siemens.comSource record
Detection Hunting Query

— No published hunting query names this record. Browse community and library queries instead.

Open KQL Library

Correlated briefings

— No published briefing references this CVE

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.