# CVE-2025-64155: Command injection in FortiSIEM

> Attackers can execute unauthorized code via crafted TCP requests in Fortinet FortiSIEM, requiring immediate patching.

- **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 Jan 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-gvhh-fvm4-vqqj

## What is CVE-2025-64155?

CVE-2025-64155 is a critical command injection vulnerability in Fortinet FortiSIEM, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiSIEM 7.4.0, FortiSIEM 7.3.0 through 7.3.4, FortiSIEM 7.1.0 through 7.1.8, FortiSIEM 7.0.0 through 7.0.4, FortiSIEM 6.7.0 through 6.7.10 may allow an attacker to execute unauthorized code or commands via  crafted TCP requests.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Fortinet Fortisiem.

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

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

## Is CVE-2025-64155 being exploited?

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

Public exploit code:

- CVE-2025-64155: Fortinet FortiSIEM Argument Injection to Remote Code Execution (github_poc): https://github.com/horizon3ai/CVE-2025-64155
- Authorized high-impact tool from CYBERDUDEBIVASH ECOSYSTEM to detect CVE-2025-64155 (FortiSIEM phMonitor Command Injection). Scans for open ports and vulnerable behaviors ethically. (github_poc): https://github.com/cyberdudebivash/CYBERDUDEBIVASH-FortiSIEM-CVE-2025-64155-Scanner
- CVE-2025-64155-hunter (github_poc): https://github.com/purehate/CVE-2025-64155-hunter
- CVE-2025-64155 (github_poc): https://github.com/Mefhika120/Ashwesker-CVE-2025-64155

## Other vulnerabilities in Fortinet FortiSIEM

- [CVE-2025-25256](https://insights.sbomify.com/CVE-2025-25256/): Command injection in FortiSIEM (critical 9.8)
- [CVE-2019-16153](https://insights.sbomify.com/CVE-2019-16153/): Hardcoded credentials in Fortinet FortiSIEM (critical 9.8)
- [CVE-2023-40714](https://insights.sbomify.com/CVE-2023-40714/): Path traversal in FortiSIEM (critical 9.7)
- [CVE-2024-23108](https://insights.sbomify.com/CVE-2024-23108/): Command injection in FortiSIEM (critical 9.7)
- [CVE-2024-23109](https://insights.sbomify.com/CVE-2024-23109/): Command injection in FortiSIEM (critical 9.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64155 is a critical command injection vulnerability in Fortinet FortiSIEM, published on 13 Jan 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-2025-64155 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-2025-64155/ (Markdown: https://insights.sbomify.com/CVE-2025-64155/index.md)
```

## Sources

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

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