# CVE-2025-54659: Path traversal in FortiSOAR Agent Communication Bridge

> Unauthenticated attackers can read files accessible to the fortisoar user via crafted requests to the agent port.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N/E:F/RL:X/RC:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-pfvw-qgrv-hgv6

## What is CVE-2025-54659?

CVE-2025-54659 is a medium-severity path traversal vulnerability in Fortinet FortiSOAR Agent Communication Bridge, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 fortisoar user on a system where the agent is deployed, via sending a crafted request to the agent port.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-54659?

It affects 1 product.


Products: Fortinet Fortisoar Agent Communication Bridge.

## How do I fix CVE-2025-54659?

No fix has been published for CVE-2025-54659 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-54659 being exploited?

There is no known exploitation of CVE-2025-54659 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54659 and fix it if it is affected.

What it is: CVE-2025-54659 is a medium-severity path traversal vulnerability in Fortinet FortiSOAR Agent Communication Bridge, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54659 in the wild and no public exploit code.

Affected product: Fortinet FortiSOAR Agent Communication Bridge. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-54659/ (Markdown: https://insights.sbomify.com/CVE-2025-54659/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54659
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54659
- OSV: https://osv.dev/vulnerability/CVE-2025-54659

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-54659/
Summaries are generated and may contain mistakes; the official description above is the record.