FortiMail CVE-2026-104286 is under active attack
Fortinet says attackers are exploiting a critical vulnerability in FortiMail. This is an immediate appliance-security issue, not a theoretical weakness to file away for the next maintenance cycle. The flaw, tracked as CVE-2026-104286, affects the product’s management interface and can let an unauthenticated attacker write arbitrary files on the underlying system through crafted HTTP or HTTPS requests.
Fortinet describes the issue as a path traversal combined with improper handling of a null byte. It carries a CVSS score of 9.8. The practical concern is unauthorized file writing, which may enable code or command execution on vulnerable devices. Fortinet has confirmed active exploitation and recommends applying workarounds until a fixed release can be installed.
The vulnerability was discovered internally by Gwendal Guégniaud of Fortinet’s Product Security team. That detail does not reduce the urgency: the vendor’s warning is that exploitation is already happening.
Which FortiMail versions are affected
The reported affected ranges 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. Administrators should check the version running on every appliance, including systems that may be managed separately from the main email infrastructure.
The remediation paths differ by branch. FortiMail 7.2 users can address the issue by upgrading to the 7.4 branch or later. For affected 7.4, 7.6, and 8.0 installations, the source reports that fixed releases were not yet available at the time of its report. Fortinet listed 7.4.9, 7.6.7, and 8.0.2 as upcoming versions containing the fix.
That timing matters. Don’t assume an update exists simply because a version number has been announced. Check Fortinet’s current advisory and release availability, then install the appropriate fixed release as soon as it is available. Until then, use the mitigations below.
Mitigate exposure while waiting for an update
Fortinet’s stated workaround is to disable IBE feature support from the FortiMail command line:
config system encryption ibe
set status disable
end
As an alternative, administrators can disable access to the FortiMail management interface from the Internet or restrict that interface to trusted private networks. That is a sensible exposure-reduction step, especially for appliances whose management plane is reachable from outside, but it is not a substitute for installing the vendor’s fix when available.
Apply the workaround deliberately and confirm the resulting configuration. Keep track of any service impact from disabling IBE, and coordinate the change with the teams responsible for mail operations. The article’s source does not specify a recovery procedure or the precise business impact of disabling the feature, so avoid assuming either; validate behavior in your own environment.
FortiMail incident response: check the published indicators
A workaround limits risk going forward; it does not establish whether an appliance was already accessed. Fortinet published indicators associated with the attacks, including files reported as added or modified. Check those paths and compare file hashes where your investigation process supports it:
| Path | Reported status | SHA-256 |
|---|---|---|
/data/lib/liblog.so | Added | 8015f34dc84922b03688399d7f9fe7a00361789f7e420c7e2a2cdb23e75cef84 |
/bin/smit | Modified | 77324ac428bde86d351fc5fc06f6d64a6bfe737dfb2743df1d4c5ac2418a5b6a |
/data/bin/webconsole | Added | 7a6cea9f5c9e2e9994d4e3c4da73f86cf5acd05ea5d312c066c9d1dafd69ee38 |
/data/bin/mailservice | Added | 4000276a150a165d3c2537d1e19fb393c4de8333076a16655e28059cae82157b |
/data/etc/httpd.conf | Modified | 703e97c64e61e41dc3aaba580d82bb2aa7b6a11b54ee6fb467ed5d5a3bffdef5 |
/data/etc/ld.so.preload | Added | 8953ec7960b09f544a880b072ad4e6cfda7a8303f486251d3478dcfdfbac23b6 |
/data/migadmin.tar.gz | Modified | d6fe51c22b91776f4c961ea58bcac5917f15d560a619d7ce726d3d51795609d3 |
The listed IP addresses associated with the attacks are 79[.]141.169.187 and 45[.]129.0.192. Treat them as investigation indicators, not as proof by themselves that a device is compromised.
Review logs and suspicious archive settings
Fortinet’s advisory includes log entries intended to help identify potentially compromised appliances. One example shows an account named archive234 configured from the command line, with 79.141.169.187 set as the remote server and /uploads as the remote directory. The report says this could indicate that the compromised appliance was configured to send archived data to a remote server.
Review appliance logs for that account and configuration, and look for the listed addresses and the file indicators above. The source also describes a cron job executing a command related to /migadmin; include that detail in the log review. Compare findings with known-good configuration and the appliance’s expected administrative activity. A match deserves investigation, but don’t overstate what a single indicator proves.
If you find suspicious files, settings, or log activity, preserve relevant evidence and follow your organization’s incident-handling process while working from Fortinet’s advisory. The cited report supplies indicators and workarounds, but does not prescribe a complete forensic or recovery playbook. Keep response decisions grounded in what your evidence shows.
A practical response sequence
First, inventory FortiMail appliances and identify any running affected releases. Second, apply Fortinet’s IBE workaround or restrict management access to trusted private networks while the relevant fixed release is unavailable. Third, examine the published file, hash, IP, and log indicators for signs of prior activity. Finally, install the vendor’s fixed release as soon as it is available for the appliance’s branch, following the current Fortinet advisory.
Do not treat mitigation as a clean bill of health. Active exploitation means exposure may have preceded the configuration change. Equally, the published indicators are a starting point rather than an exhaustive account of every possible artifact. Keep the appliance under review, document changes and findings, and use the vendor’s updated guidance to direct the next step.
fortimail cve-- is under active attack
fortimail cve-- is under active attack