Fortinet is warning customers that a critical FortiMail vulnerability, CVE-2026-104286, has been exploited in the wild before a fix was available. The flaw combines path traversal (CWE-22) and improper neutralization of NULL bytes (CWE-158) and “may allow an unauthenticated attacker to write arbitrary files on the underlying system via crafted HTTP or HTTPS requests,” according to Fortinet’s advisory FG-IR-26-175, published Oct. 1. Fortinet rates it critical with a CVSSv3 score of 9.8, lists the affected component as the GUI and says the impact is execution of unauthorized code or commands.
Affected releases are FortiMail 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, 7.4.0 through 7.4.8 and 7.2.0 through 7.2.9. Fortinet lists fixes in upcoming versions 8.0.2, 7.6.7 and 7.4.9, which had not been released, and tells 7.2 users to move to the 7.4 branch or later. SecurityWeek (opens in new tab) reported that Fortinet has not given a release timeline.
Until patches ship, the advisory urges customers to disable FortiMail’s IBE (identity-based encryption) feature. Alternatives it lists are disabling access to the FortiMail webmail interface from the internet or limiting it to trusted private networks, or, where a web application firewall sits in front of FortiMail, blocking POST requests to /ibe that contain “../”. BleepingComputer (opens in new tab), SecurityWeek (opens in new tab), Help Net Security (opens in new tab) and The Register (opens in new tab) described the access workaround as applying to the management interface. The Register (opens in new tab) noted that applying a workaround will not remove files or persistence that attackers may already have planted.
Fortinet published indicators of compromise, including attacker-linked IP addresses 79.141.169.187 and 45.129.0.192 and sample log entries. One entry shows an archive account named archive234 configured from the command line to send data to a remote server at 79.141.169.187, which BleepingComputer (opens in new tab) said could indicate attackers set up compromised appliances to send archived data off-site. CISA added the flaw to its Known Exploited Vulnerabilities catalog on Oct. 1 and set an Oct. 4 due date, requiring federal agencies to apply mitigations under Binding Operational Directive 26-04 and to perform forensic triage.
Fortinet said the bug was discovered internally by Gwendal Guégniaud of its Product Security team. The company has not said when exploitation began, how many systems were compromised or who is behind the attacks. Asked by BleepingComputer (opens in new tab) for details, Fortinet pointed to the advisory and said: “Consistent with Fortinet’s commitment to responsible PSIRT disclosure and public-private partnerships, we are communicating with relevant government organizations, including CISA, on the content of this advisory.”