CVE-2026-104286: FortiMail Zero-Day Is Being Exploited - Workaround and Compromise Assessment
Fortinet reports a critical, actively exploited path traversal vulnerability in FortiMail 7.2 through 8.0 (CVE-2026-104286, CVSS 9.8). Fixed versions 7.6.7, 7.4.9, and 8.0.2 have been available since October 2 and 3, respectively. Until updating, the workaround disables IBE or blocks the webmail interface from the Internet; indicators for compromise assessment are also available.
On October 1, 2026, Fortinet published advisory FG-IR-26-175 regarding a critical vulnerability in FortiMail. Through crafted HTTP or HTTPS requests, an unauthenticated attacker can write arbitrary files to the underlying system and thereby execute code. The vulnerability is tracked as CVE-2026-104286 and has a CVSS score of 9.8. Fortinet confirms that it is already being exploited; the U.S. agency CISA added it to its Known Exploited Vulnerabilities (KEV) catalog the same day. At the time of the advisory, only a workaround was available. FortiMail 7.6.7 has been available since October 2, 2026, and 7.4.9 and 8.0.2 since October 3, 2026; Fortinet has listed these versions as the solution in the advisory since October 5.
Assistance with the workaround and assessment
If you need help implementing the workaround, assessing compromise, or performing the subsequent update, please use the contact form on adeptio.ch. I can also respond on short notice.
Certified: Fortinet FortiMail 7.4 Administrator
I am certified by Fortinet as a FortiMail 7.4 Administrator. The exam covers deployment, administration, ongoing operations, and troubleshooting of FortiMail. View badge on Credly
Key points at a glance
| Feature | Details |
|---|---|
| Advisory | FG-IR-26-175, published October 1, 2026 |
| CVE | CVE-2026-104286 |
| Rating | CVSS 3.1: 9.8 (critical), AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Vulnerability type | Path traversal (CWE-22) and insufficiently filtered NULL characters (CWE-158) |
| Prerequisite | no authentication, HTTP or HTTPS access to the web interface |
| Component according to the advisory | GUI |
| Exploitation | confirmed; in CISA KEV since October 1, 2026 |
| Update | 7.6.7 (since October 2), 7.4.9 and 8.0.2 (since October 3); no fix for 7.2 |
| Workaround | disable IBE, block the webmail interface from the Internet, or filter through a WAF |
| Discovered by | Fortinet internally (Gwendal Guégniaud) |
Timeline
All times are in Central European Summer Time (CEST). Where no time is given, no reliable time information is available.
-
Wed, October 1
Advisory FG-IR-26-175
Fortinet publishes the advisory with affected versions, workaround, and indicators. Exploitation is already known at this point; according to the advisory, no virtual patch for FortiGate IPS is available.
-
Wed, October 1, 08:46
Report by heise online
heise reports on the ongoing attacks and the workaround; according to the report, updates to close the vulnerability are not yet available.
-
Wed, October 1
Added to the CISA catalog
CISA adds CVE-2026-104286 to the Known Exploited Vulnerabilities catalog. According to BleepingComputer and The Hacker News, U.S. federal agencies must implement updates or workarounds by October 4.
-
Thu, October 2
FortiMail 7.6.7 released
Fortinet publishes the release notes for FortiMail 7.6.7.
-
Fri, October 3
FortiMail 7.4.9 and 8.0.2 released
Fortinet publishes the release notes for FortiMail 7.4.9 and 8.0.2. By this date, Fortinet had also changed the advisory without an entry in the revision history: the alternative block now applies to the webmail interface instead of the administration interface, a WAF rule has been added, and the list of files with hash values has been removed.
-
Mon, October 5
Advisory with solution, FortiMail Cloud fixed
Fortinet adds the fixed versions as the solution in the advisory. According to the advisory, Fortinet updated FortiMail Cloud to 7.6.7 and 8.0.2, respectively, on the same day; cloud customers do not need to take any action.
-
As of Sun, October 25
Still unresolved
The advisory contains no information on the scope of the attacks, affected organizations, or the origin of the attackers.
Affected versions
| Branch | Affected | Solution according to the advisory |
|---|---|---|
| FortiMail 8.0 | 8.0.0 through 8.0.1 | Update to 8.0.2 or later |
| FortiMail 7.6 | 7.6.0 through 7.6.6 | Update to 7.6.7 or later |
| FortiMail 7.4 | 7.4.0 through 7.4.8 | Update to 7.4.9 or later |
| FortiMail 7.2 | 7.2.0 through 7.2.9 | no fix in the 7.2 branch; move to 7.4 or later |
No update will be released for the 7.2 branch; these systems must move to 7.4 or later. Refer to the release notes for the applicable branch for the upgrade path to the fixed version. The workaround remains necessary until the update has been installed.
The CLI displays the current version with:
get system status
Immediate action: Implement the workaround
Fortinet provides two options. According to the advisory, either one is sufficient; where operations permit, both make sense. The workaround is only necessary until the fixed version is installed.
Option 1: Disable IBE
IBE (Identity-Based Encryption) is the feature FortiMail uses to deliver encrypted messages to external recipients: the recipient receives the message as an encrypted attachment (push) or retrieves it through the FortiMail web portal (pull). Fortinet identifies the IBE feature as the workaround, so attacks run through a code path of this feature. Disable it in the GUI under Encryption > IBE (set IBE Service to “off”) or in the CLI:
config system encryption ibe
set status disable
end
Check the status before and after with:
show system encryption ibe
Disabling it affects mail traffic. Fortinet does not describe these effects in the advisory. Before making the change, you should therefore determine:
-
Which policies use IBE: IBE is configured as an encryption action in content and policy profiles, for example for subject keywords such as
[secure]or for data protection rules. These messages can no longer be delivered encrypted via IBE while it is disabled. -
How these messages should be handled: hold them, deliver them using a different method (S/MIME, mandatory TLS), or notify senders. Unencrypted delivery of messages that a policy is intended to encrypt is generally not permitted.
-
Who is affected: External recipients retrieving messages through the IBE portal and users sending encrypted messages should be informed.
Option 2: Block the webmail interface from the Internet
The second option blocks Internet access to the webmail interface or limits it to trusted private networks, such as a management network or VPN. In the first version of the October 1 advisory, Fortinet referred to the administration interface here; the current version refers to the webmail interface. This can be implemented on an upstream firewall or through the interface access settings in FortiMail (Administrative Access). If a Web Application Firewall is in front of FortiMail, the advisory identifies another option: block POST requests to /ibe that contain ../.
User quarantine access, the IBE portal, and administration also run over HTTPS. If they are on the same interface as webmail, a blanket HTTPS block also blocks these services. In this case, option 1 is the more direct approach. SMTP on port 25 is unaffected by either option; mail flow continues.
Assessing compromise
Because the vulnerability was exploited before the advisory, the workaround does not rule out an earlier attack. Fortinet publishes indicators in the advisory that can be used to assess a system.
Files
In the first version of the October 1 advisory, Fortinet listed the following files as findings on compromised systems, each with MD5 and SHA256 hashes. The current version lists only IP addresses and log entries; the original list with hash values can be viewed in the archived version of the advisory (see Sources).
| Path |
|---|
/data/lib/liblog.so |
/data/etc/ld.so.preload |
/bin/smit |
/data/bin/webconsole |
/data/bin/mailservice |
/data/etc/httpd.conf |
/data/migadmin.tar.gz |
An entry in /data/etc/ld.so.preload preloads the specified library into every process. Together with liblog.so, this indicates a persistent backdoor that survives a reboot.
IP addresses
| Address |
|---|
79.141.169.187 |
45.129.0.192 |
These addresses should be searched for in the logs of FortiMail, the upstream firewall, and the reverse proxy, and blocked until further notice.
Log entries
The advisory identifies three patterns in FortiMail system logs:
-
Cron entries for user
rootthat launch a shell relating to/migadmin, such astype=event subtype=system pri=debug user=system ui=cron msg="(root) CMD (/bin/sh -c 'O=/migadmin.... -
Configuration of archive accounts with remote IP
79.141.169.187. An archive account can store copies of messages at an external destination. -
Base64 decoding errors in the IBE decrypter and conspicuous failed login attempts.
Hits for any of these indicators mean the system is considered compromised. Before making any changes, preserve logs and configuration so that forensic analysis remains possible. An update alone does not remove an installed backdoor. Remediation includes reinstalling from a trusted source, importing a verified configuration, and changing all credentials stored on the system: administrator accounts, LDAP bind accounts, SMTP authentication credentials, and private certificate keys. Archive accounts and forwarding rules should be checked for unknown destinations, because message contents can be exfiltrated through them.
Context
Mail gateways sit at the network edge and process an organization’s entire message traffic. A vulnerability that executes code without authentication gives an attacker access to message contents, stored credentials, and key material. This is not the first case involving FortiMail: in May 2025, CVE-2025-32756 (FG-IR-25-254, CVSS 9.6) affected FortiMail as well as FortiVoice; at the time, the vulnerability was demonstrably exploited on FortiVoice systems.
At the end of September, Kiteworks also urged its customers to shut down their systems as a precaution due to a warning from law enforcement agencies; the background remains unclear (Kiteworks: shutdown recommendation on September 26). No connection between the two cases is known.
What to do now
-
Determine the version with
get system statusand compare it with the table of affected versions. -
Check indicators and preserve logs before making changes to the system.
-
Implement the workaround until the update is installed: disable IBE or block the webmail interface from the Internet, after clarifying the effects on encrypted delivery.
-
Block IP addresses and search firewall logs retrospectively.
-
Install the update: Install 8.0.2, 7.6.7, or 7.4.9 (or later); move systems on 7.2 to 7.4 or later.
-
Monitor the advisory: Fortinet will add new findings to FG-IR-26-175; the revision history is at the end of the advisory.
Change history
- October 25, 2026: Added: fixed versions 7.6.7 (October 2, 2026), 7.4.9, and 8.0.2 (October 3, 2026), as well as the FortiMail Cloud update. According to the revised advisory, the block applies to the webmail interface rather than the administration interface, supplemented by a WAF rule; the file list with hash values is now only included in the archived version.
Comments
Comments are loaded from GitHub / Giscus.