1-minute read of a 4 min report

Fortinet FortiMail Attackers Write Files Through Its Web Interface

By

1-minute read

What a defender needs to know

CISA added CVE-2026-104286 to its exploited-vulnerabilities catalog on October 1, with an October 4 action date. Fortinet says unauthenticated HTTP or HTTPS requests can exploit path traversal and NULL-character handling in FortiMail’s GUI to write arbitrary files on the appliance. The company reports exploitation in the wild and supplies file and log indicators. Fortinet found the flaw internally; Gwendal Guégniaud is credited.

Inventory FortiMail appliances and their installed versions. Fortinet lists affected branches 8.0.0–8.0.1, 7.6.0–7.6.6, 7.4.0–7.4.8 and 7.2.0–7.2.9. Its 8.0.2, 7.6.7 and 7.4.9 release targets are upcoming; 7.2 operators should plan a move to a remediated build on 7.4 or later; 7.4.0–7.4.8 remain affected. The CVE JSON carries older conflicting targets, so follow the current PSIRT table and confirm branch-specific guidance for 7.0 systems.

Restrict management access to a trusted private network, or set config system encryption ibe to set status disable as Fortinet instructs. Where feasible, use both and verify the disabled setting and the blocked management route from an untrusted network. Forensic triage is separate: compare appliance files such as /data/etc/ld.so.preload and /data/lib/liblog.so with Fortinet’s published hashes, and inspect ui=cron events and archive configuration for remote-ip[79[.]141[.]169[.]187]. Preserve and investigate a match before returning that appliance to service; an installed-build check alone misses files written earlier.

Primary sources