Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:NSummary
CVE-2025-54659 is a medium-severity Path Traversal (CWE-22) vulnerability in Fortinet Fortisoar Agent Communication Bridge. Its CVSS base score is 5.8 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-54659 is an Improper Limitation of a Pathname to a Restricted Directory (Path Traversal) vulnerability (CWE-22) in Fortinet FortiSOAR Agent Communication Bridge version 1.1.0 and all versions of 1.0. The flaw allows an unauthenticated attacker to read files accessible to the "fortisoar" user on systems where the agent is deployed by sending a crafted request to the agent port. Published on 2026-03-10, it carries a CVSS v3.1 base score of 5.8 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N), indicating moderate severity with network accessibility, low attack complexity, no privileges or user interaction required, and low confidentiality impact in a scoped scenario.
An unauthenticated attacker who can reach the agent's listening port over the network can exploit this vulnerability remotely. By crafting a malicious request that traverses path restrictions, the attacker gains read access to arbitrary files permitted to the fortisoar user account on the host system, potentially exposing sensitive configuration data, logs, or other information depending on the deployment environment and permissions.
Fortinet has issued security advisory FG-IR-26-084, available at https://fortiguard.fortinet.com/psirt/FG-IR-26-084, which provides details on the vulnerability, affected versions, and recommended mitigation actions for security practitioners.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-208491
Vulnerability Data
An Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability [CWE-22] vulnerability in Fortinet FortiSOAR Agent Communication Bridge 1.1.0, FortiSOAR Agent Communication Bridge 1.0 all versions may allow an unauthenticated attacker to read files accessible to the…
more
fortisoar user on a system where the agent is deployed, via sending a crafted request to the agent port.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.