Skip to main content
All incident reports
Incident report

Fortinet warns critical FortiMail zero-day is being exploited, patches pending

Fortinet has disclosed a critical path traversal and NULL-byte flaw in the FortiMail management interface that lets unauthenticated attackers write files on the appliance, and says it has been exploited in attacks. Fixed builds for the 7.4, 7.6 and 8.0 branches have not shipped, so customers are left with workarounds and indicators of compromise.

· First published

The short version

  • The flaw. CVE-2026-104286 is a path traversal and NULL-byte handling flaw rated 9.8 that allows an unauthenticated attacker to write arbitrary files to the underlying system through crafted HTTP or HTTPS requests to the FortiMail management interface. Fortinet says this may lead to unauthorised code or command execution.
  • Exploitation. Fortinet says the flaw has been exploited in the wild, and CISA added it to its Known Exploited Vulnerabilities catalogue on 1 October. Neither Fortinet nor CISA has described the attacks or named the attackers.
  • Affected versions. FortiMail 7.2.0 to 7.2.9, 7.4.0 to 7.4.8, 7.6.0 to 7.6.6 and 8.0.0 to 8.0.1 are affected. Fixes are listed for 7.4.9, 7.6.7 and 8.0.2, which are not yet released; 7.2 users should move to the 7.4 branch or later.
  • Interim measures. Fortinet tells administrators to disable identity-based encryption support or to block access to the management interface from the internet, and has published two IP addresses, file hashes and log entries to hunt with. One log example shows an archive account configured to send data to an external server.

Timeline

DateEvent
1 OctoberFortinet publishes an advisory on CVE-2026-104286 stating that it has been exploited in the wild, and CISA adds the flaw to its Known Exploited Vulnerabilities catalogue the same day.
2 OctoberSecurityWeek reports that no patch has been released and that Fortinet has given no timeline for the fixed versions.

The vulnerability

Fortinet's advisory describes CVE-2026-104286 as a path traversal flaw combined with improper handling of NULL bytes, rated 9.8 on the CVSS scale. Fortinet says an unauthenticated attacker can send crafted HTTP or HTTPS requests to the FortiMail management interface and write arbitrary files on the underlying system, which the company says may allow unauthorised code or command execution. Gwendal Guégniaud of Fortinet's Product Security team found the flaw internally.

The affected releases are FortiMail 7.2.0 to 7.2.9, 7.4.0 to 7.4.8, 7.6.0 to 7.6.6 and 8.0.0 to 8.0.1. Fixed builds are listed as 7.4.9, 7.6.7 and 8.0.2; SecurityWeek reported that Fortinet gave no release timeline for them. Customers on 7.2 are told to move to the 7.4 branch or later. Until then Fortinet offers two workarounds: disable identity-based encryption (IBE) support, or restrict the management interface to trusted private networks.

Exploitation and detection

Fortinet says the flaw has been exploited in the wild and published indicators of compromise alongside the advisory. CISA added CVE-2026-104286 to its Known Exploited Vulnerabilities catalogue on 1 October. Neither Fortinet nor CISA has described the observed attacks. Asked for more detail, Fortinet pointed to the advisory and said it is communicating with government organisations, including CISA, about its contents.

The published indicators include two IP addresses, 79.141.169.187 and 45.129.0.192, and files added to or modified on compromised systems; the hashes are in the advisory. Fortinet also released log entries for hunting, among them a command-line change that created an archive account named archive234 pointing at 79.141.169.187 with the remote directory /uploads. This could indicate that an attacker set the appliance to send archived data to a remote server. Other entries show a cron job, an administrator logout, an IBE decryption error and failed logins.

What is not known yet

  • Who carried out the attacks and where they operated from.
  • When exploitation began and how long affected appliances were exposed before the advisory.
  • How many FortiMail installations were compromised.
  • Whether mail or archived data was actually taken; Fortinet says the archive account in its log example could indicate exfiltration but does not confirm it.
  • Which organisations, sectors or countries the victims belong to.

What to do

If you run FortiMail

  1. Check whether your version is affected: 7.2.0 to 7.2.9, 7.4.0 to 7.4.8, 7.6.0 to 7.6.6 and 8.0.0 to 8.0.1 are in scope.
  2. Until a fix is available, disable identity-based encryption support using the commands in Fortinet's advisory, or cut off access to the management interface from the internet and allow only trusted private networks.
  3. Plan to move to FortiMail 7.4.9, 7.6.7 or 8.0.2 when released; installations on 7.2 should upgrade to the 7.4 branch or later.
  4. Hunt on the appliance for the published indicators: the two IP addresses, the added or modified files and any archive account configured to send data to an external server, taking hashes from the advisory.

For everyone else

  1. Keep the management interfaces of mail gateways and other edge appliances off the public internet and reachable only from trusted networks.
  2. Treat vendor workarounds as temporary and install the fixed release as soon as it ships.
  3. Review appliance logs for new local accounts, unexpected scheduled jobs and outbound transfers to unfamiliar servers.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.