CVE-2025-64155: Unauthenticated Remote Command Injection in Fortinet FortiSIEM phMonitor
- Vendor
- Fortinet
CVE-2025-64155 is an unauthenticated OS command injection vulnerability in the Fortinet FortiSIEM phMonitor service on TCP port 7900. Command handlers registered through phMonitorProcess::initEventHandler are remotely accessible without authentication. An Elasticsearch storage-request handler passes attacker-controlled parameters into a shell-script workflow that invokes curl, permitting argument injection and arbitrary file writes with admin privileges. Overwriting an executable enables code execution as admin; overwriting an admin-writable script executed periodically by a root cron job enables escalation to root. Affected releases are 7.4.0, 7.3.0–7.3.4, 7.2.0–7.2.6, 7.1.0–7.1.8, 7.0.0–7.0.4, and 6.7.0–6.7.10. Only Super and Worker nodes are affected; Collector nodes, FortiSIEM Cloud, and FortiSIEM 7.5 are unaffected by this vulnerability. Public proof-of-concept code and active exploitation have been reported.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits unauthenticated remote code execution as the admin user and, through the demonstrated file-overwrite privilege-escalation chain, root-level appliance compromise. This can compromise the confidentiality, integrity, and availability of the SIEM platform, enabling sensitive-data theft, modification of collected security information, persistence, and service disruption. A compromised appliance may also provide a foothold for lateral movement into connected internal networks.
Mitigation
If you can’t patch tonight, do this now.
Until patched, restrict access to phMonitor on TCP port 7900 to trusted systems using firewall rules. Place FortiSIEM in a protected network segment and prevent direct public-internet access. Monitor for anomalous phMonitor requests, unexpected executable modifications, and cron-job tampering, and investigate suspected exploitation.
Remediation
Patch, then assume compromise.
Apply Fortinet's fixes: upgrade 7.4.0 to 7.4.1 or later, 7.3.0–7.3.4 to 7.3.5 or later, 7.2.0–7.2.6 to 7.2.7 or later, and 7.1.0–7.1.8 to 7.1.9 or later. Migrate affected 7.0 and 6.7 installations to a supported fixed release. Validate the upgrade on affected Super and Worker nodes. Assess previously exposed systems for compromise; patching does not remove existing attacker access or malicious modifications.
Exploits
1 exploit validated by Mallory's analysis. Hidden: 4 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2025-64155 exploited in the wild?
- Yes. As of Oct 23, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2025-64155?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-64155, the earliest disclosed Jan 13, 2026.
- Is there a patch for CVE-2025-64155?
- Apply Fortinet's fixes: upgrade 7.4.0 to 7.4.1 or later, 7.3.0–7.3.4 to 7.3.5 or later, 7.2.0–7.2.6 to 7.2.7 or later, and 7.1.0–7.1.8 to 7.1.9 or later. Migrate affected 7.0 and 6.7 installations to a supported fixed release.
- What products are affected by CVE-2025-64155?
- Fortinet Fortisiem.
- How severe is CVE-2025-64155?
- CVE-2025-64155 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 43.9% (99th percentile) as of Oct 23, 2026.
Recent activity
117 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.