critical Cve 2026 104286 · Exploits

Exploited FortiMail Flaw Now Patched: Check for Compromise First

Data graphic: poster 'FortiMail patched: check for compromise', CVSS 9.8; fixed builds 8.0.2, 7.6.7 and 7.4.9; FortiMail 7.2 gets no fix; still exploited and on the CISA KEV catalog.
AK

Threat intelligence editor · Published Oct 2, 2026 · Updated Oct 11, 2026, 8:00 PM EDT

Fortinet released FortiMail 8.0.2, 7.6.7 and 7.4.9 for exploited CVE-2026-104286 (CVSS 9.8). Check for compromise before upgrading; 7.2 gets no fix.

Fortinet says attackers are already exploiting a critical flaw in FortiMail, its email security gateway. When we first published, there was no fixed build; there now is (see the update below). CVE-2026-104286 lets an unauthenticated attacker write arbitrary files on the appliance with crafted HTTP or HTTPS requests. Fortinet rates it CVSS 9.8.

Fortinet published advisory FG-IR-26-175 on 1 October 2026 (we covered the earlier FortiVoice zero-day). CISA added the CVE to its Known Exploited Vulnerabilities catalog the same day and gave federal agencies until 4 October to act. Every supported FortiMail branch is affected, and the 7.2 branch will not get a fix at all. Before the fixed builds shipped, the only protection was Fortinet's workaround: switch off Identity Based Encryption (IBE), take the FortiMail webmail interface off the internet, or block malicious requests to /ibe at a web application firewall. That workaround still applies where you cannot patch yet.

Update (2026-10-10): Fortinet has released the fixed builds. Advisory FG-IR-26-175 now lists FortiMail 8.0.2, 7.6.7 and 7.4.9 as the patched versions, and says it fixed FortiMail Cloud on 5 October by moving all firmware to 7.6.7 or 8.0.2, so Cloud customers need to do nothing. FortiMail 7.2 still gets no fix: move to 7.4 or later. The flaw is still exploited and still on CISA's KEV catalog. Check for compromise before you upgrade, because patching does not remove an implant that is already there. This article was first published on 2 October, when no fixed build existed; the sections below are updated to match.

What is affected

The advisory lists four branches. For the first three, Fortinet has now released fixed builds.

BranchAffectedFortinet's solution
FortiMail 8.08.0.0 to 8.0.1Upgrade to 8.0.2 or above
FortiMail 7.67.6.0 to 7.6.6Upgrade to 7.6.7 or above
FortiMail 7.47.4.0 to 7.4.8Upgrade to 7.4.9 or above
FortiMail 7.27.2.0 to 7.2.9Upgrade to branch 7.4 or above

The 7.2 row is the hard one. Those customers must plan a branch migration. They also need the workaround in place until the move is done, and the target must be 7.4.9 or later, because earlier 7.4 builds are themselves vulnerable. FortiMail Cloud was fixed by Fortinet on 5 October.

There is a second wrinkle. The machine-readable record Fortinet filed with NVD lists FortiMail 7.0.0 through 7.0.9 among the affected builds as well, but the advisory's table does not mention 7.0. If you still run 7.0, treat the appliance as exposed and apply the workaround.

How the flaw works

Fortinet describes two weaknesses chained together: a path traversal (CWE-22) and improper neutralisation of a NULL byte (CWE-158). A crafted request steps outside the directory the web service should write to. Mishandled NULL bytes are a classic way to cut a file name short after it has passed a check. Fortinet has not published the exact request.

The vulnerable code sits behind IBE, the FortiMail feature that lets recipients outside the organisation open encrypted mail through a web portal. That is why disabling IBE is the main workaround. It is also why the exposure is wide: IBE only works if outside recipients can reach the portal, so it is internet-facing by design.

An arbitrary file write on an appliance is usually one step from code execution. The indicators Fortinet published show attackers taking that step.

What the attackers left behind

Fortinet's indicators point to implants and persistence, not just a dropped file. Fortinet listed these files, with hashes, when it published the advisory on 1 October and has since removed that list from the advisory page, which now keeps the IP addresses and log patterns. The file list below comes from the archived 2 October copy:

  • /data/etc/ld.so.preload added. It makes the system load an attacker library into every process.
  • /data/lib/liblog.so added. It is a shared library, most likely the one the preload file points to.
  • /bin/smit modified, and /data/bin/webconsole and /data/bin/mailservice added: replaced and new binaries.
  • /data/etc/httpd.conf modified, and /data/migadmin.tar.gz modified: the web server configuration and the admin interface archive.

Fortinet also lists two source IPs, 79.141.169.187 and 45.129.0.192, and log patterns to search for:

  • a cron entry running as root that starts /bin/sh -c 'O=/migadmin
  • an admin logout "from (null)"
  • an archive account configured with remote-ip[79.141.169.187], which would copy mail out to the attacker
  • in the encryption logs, Invalid Base64 Encoding at pos 0 buffer exceptions and failed internal-user logins

The archive account is the most serious finding for most organisations. An email gateway sees every message, so a rogue archive rule is quiet, ongoing data theft.

Fortinet has not named the attacker, and nobody has published victim counts. CISA marks the entry as requiring forensic triage under BOD 26-04. That means checking for compromise as well as mitigating.

Data graphic: advisory timeline for CVE-2026-104286. 1 October advisory published and added to CISA KEV; 4 October KEV due date passed; 5 October solution update lists fixed builds 8.0.2, 7.6.7 and 7.4.9 and FortiMail Cloud is fixed; 7 October advisory clarifies Cloud needs no customer action.

Fortinet's advisory and the CISA KEV listing landed on the same day. The advisory's solution was updated on 5 October with the fixed builds, and on 7 October it clarified that FortiMail Cloud is already fixed.

What defenders should do

  1. Find every FortiMail you run, including 7.0 and 7.2 boxes and anything in a forgotten DMZ.
  2. Disable IBE now if you can live without it. In the GUI, go to Encryption, then IBE, then IBE Service, and set it to off. From the CLI:
config system encryption ibe
set status disable
end
  1. If IBE has to stay on, disable access to the FortiMail webmail interface from the internet, or limit access to trusted private networks. Fortinet's advisory now also offers a third option: if a web application firewall sits in front of FortiMail, block POST requests to /ibe that contain ../.
  2. Hunt before you assume you are clean. Check for the seven files above. Fortinet published their SHA-256 hashes on 1 October and has since removed the file list and hashes from the advisory; an archived copy from 2 October still has them. Search the logs for the two IPs, root cron jobs touching /migadmin, and archive accounts you did not create. Review all archive and forwarding rules.
  3. If you find any indicator, treat the appliance as compromised. Preserve the disk and logs, rebuild from a clean image rather than deleting files, and rotate the admin credentials and any keys stored on the box. Assume archived mail was read.
  4. Install 8.0.2, 7.6.7 or 7.4.9 once the hunt in step 4 is done, and keep the workaround until you have. On 7.2, schedule the move to a fixed 7.4 or later build.

Data graphic: Fortinet's indicators of compromise for CVE-2026-104286. Seven files added or modified, four mapped ld.so.preload, liblog.so, /bin/smit, httpd.conf , plus the addresses 45.129.0.192 and 79.141.169.187, the second set as a rogue archive target.

Fortinet's indicators as first published: seven files added or modified, two IP addresses and a rogue archive account. Fortinet has since removed the file list from the advisory. Any hit means rebuilding the appliance.

The KEV due date for federal civilian agencies was 4 October 2026 and has passed, so any FortiMail that is neither patched nor mitigated is overdue. Everyone else should treat it the same way.

Fortinet credits Gwendal Guégniaud and the Fortinet Product Security Team with the finding.

Sources

Keep reading

All latest →
  1. criticalExploitsExploited FreeSWITCH Flaw Turns One SIP MESSAGE Into Command Execution: Update to 1.11.34 min
  2. highExploitsFortiManager FGFM Flaw Lets Unauthenticated Attackers Run Code5 min
  3. highExploitsAnthropic's Scanner and Google Both Found a Critical Apache httpd mod_http2 RCE: Update to 2.4.714 min
  4. highExploitsMalbear Says an AI Agent Breached a Telco via Cisco BroadWorks CVE-2026-20320; CISA Lists It, Cisco Sees No Evidence5 min
  5. criticalExploitsCheck Point Gaia Root Flaw Is Exploited, and Attackers Chained It With PHP2Shell to Wipe ESXi Hosts4 min
  6. highExploitsNovember 2026 Patch Tuesday: Patch the Exploited Outlook Hash Leak First, Then Two Zero-Click 9.8 RCEs4 min