# CVE-2026-106173: Path traversal in FortiSIEM

> Attackers can execute unauthorized code or commands via specially crafted packets due to a path traversal vulnerability in FortiSIEM.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-5cx2-chqq-627m

## What is CVE-2026-106173?

CVE-2026-106173 is a critical path traversal vulnerability in Fortinet FortiSIEM, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiSIEM 7.5.0 may allow attacker to execute unauthorized code or commands via specially crafted packets.

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

## Which versions are affected by CVE-2026-106173?


## How do I fix CVE-2026-106173?

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

## Is CVE-2026-106173 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-106173 exists.

Public exploit code:

- Proof of concept exploit for CVE-2026-106173, a path traversal file write leading to RCE for Fortinet FortiSIEM (github_poc): https://github.com/horizon3ai/CVE-2026-106173
- CVE-2026-106173 – FortiSIEM phQueryMaster RCE (CVSS 9.8) | Red/Blue Team suite for unpatched FortiSIEM 7.5.0. 2 tools: Full Exploit (multi-primitive RCE, reverse shell, persistence, creds, readback, mass scan, Tor), Blue Team Checker (exposure detection, HTTP/2 fingerprint, reporting, audit). Only Use Ethically, Stay Legal <3 (github_poc): https://github.com/tc4dy/CVE-2026-106173-PoC-Exploit
- CVE-2026-106173 (github_poc): https://github.com/0xredash/CVE-2026-106173
- Proof of concept exploit for CVE-2026-106173, a path traversal file write leading to RCE for Fortinet FortiSIEM (github_poc): https://github.com/MRdark-ops/rce-FortiSIEM
- Python PoC for CVE-2026-106173  unauthenticated path-traversal file write in FortiSIEM's QueryResult gRPC handler. (github_poc): https://github.com/aduli198/CVE-2026-106173

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-106173 and fix it if it is affected.

What it is: CVE-2026-106173 is a critical path traversal vulnerability in Fortinet FortiSIEM, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-106173 exists.

Affected product: Fortinet FortiSIEM. 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-2026-106173/ (Markdown: https://insights.sbomify.com/CVE-2026-106173/index.md)
```

## Sources

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

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