FortiMail CVE-2026-104286 Exploited: Upgrade to Fixed Releases (8.0.2 / 7.6.7 / 7.4.9)
Security

FortiMail CVE-2026-104286 Exploited: Upgrade to Fixed Releases (8.0.2 / 7.6.7 / 7.4.9)

An unauthenticated path traversal and null-byte flaw lets attackers write files to FortiMail and plant an implant. CVSS 9.8, exploited in the wild; Fortinet updated FG-IR-26-175 on 5 October with fixed releases (8.0.2 / 7.6.7 / 7.4.9; 7.2 must move to 7.4+). CISA KEV deadline was 4 October.

fortinetcve-2026-104286fortimailpath traversalcisa kev

What Happened

On 1 October 2026, Fortinet published advisory FG-IR-26-175 for CVE-2026-104286, a critical unauthenticated flaw in the FortiMail secure email gateway. The advisory states plainly that the issue "has been reported to be exploited in the wild" and urges customers to apply the workaround immediately. CISA added the CVE to its Known Exploited Vulnerabilities catalog the same day, setting a remediation deadline of 4 October 2026 for federal civilian agencies under Binding Operational Directive 26-04.

The vulnerability carries a CVSS 3.1 base score of 9.8 with the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Fortinet classifies it as two weaknesses working together: CWE-22, a path traversal, and CWE-158, improper neutralization of a NULL byte. In combination they let an unauthenticated attacker write arbitrary files to the underlying system through crafted HTTP or HTTPS requests to the management GUI. Fortinet credits internal discovery to Gwendal Guégniaud of its Product Security team, and NVD's SSVC decision marks exploitation as active, automatable as yes, and technical impact as total.

Fortinet has not said when the attacks began, how many customers were hit, or who is behind them. What the advisory does provide is an unusually detailed set of indicators of compromise, which tells you the vendor has forensic artifacts from real intrusions rather than a theoretical proof of concept.

How the File Write Works

The flaw lives in the FortiMail management interface, the component Fortinet labels simply "GUI." A path traversal lets an attacker aim a write outside the directory the web server is supposed to confine it to. The NULL byte neutralization failure is the second half of the primitive: a terminator embedded in the request manipulates how the filename is parsed, which is a classic way to defeat extension checks and land a file at a chosen path. Together they turn "upload something to a scratch directory" into "write a file of my choosing anywhere the web process can reach."

Fortinet's IoC list shows what attackers did with that primitive. They dropped a shared object at /data/lib/liblog.so and registered it through /data/etc/ld.so.preload, the Linux mechanism that forces a library to load into every dynamically linked process. That is how a single file write becomes persistent code execution on the appliance. Other artifacts include added binaries at /data/bin/webconsole and /data/bin/mailservice, a modified /bin/smit, and a tampered /data/etc/httpd.conf. One system event log in the advisory shows the intruder adding an archive account named archive234 pointed at a remote host, 79.141.169.187, to exfiltrate mail. A second attacker IP, 45.129.0.192, also appears. The jump from a write primitive to a running implant is the subject of our explainer, How an Arbitrary File Write Becomes Code Execution Through ld.so.preload.

Who Is Affected

Every on-premises FortiMail appliance running an affected build is exposed if its management interface is reachable. Fortinet's fixed-version table is the authoritative source:

  • FortiMail 8.0.0 through 8.0.1: upgrade to 8.0.2 or above
  • FortiMail 7.6.0 through 7.6.6: upgrade to 7.6.7 or above
  • FortiMail 7.4.0 through 7.4.8: upgrade to 7.4.9 or above
  • FortiMail 7.2.0 through 7.2.9: upgrade to branch 7.4 or above

Fortinet updated FG-IR-26-175 on 5 October with fixed releases. Upgrade FortiMail 8.0 to 8.0.2 or above, 7.6 to 7.6.7 or above, and 7.4 to 7.4.9 or above; systems on 7.2 must move to the 7.4 branch or later. FortiMail Cloud was remediated by Fortinet on 5 October. Keep the IBE-disable or restricted-webmail workaround in place only until the appliance is running a fixed build.

The risk is not limited to the mailflow this box carries. A secure email gateway terminates TLS, scans content, stores quarantined and archived messages, and often holds the keys for encrypted delivery. Root on that appliance is read access to a large volume of corporate mail and a foothold inside the security perimeter.

Immediate Actions

Upgrade to the fixed release for your branch now. Keep Fortinet's workaround in place only until the appliance is confirmed on 8.0.2 or above, 7.6.7 or above, or 7.4.9 or above; FortiMail 7.2 must move to 7.4 or later. The advisory gives two temporary mitigations:

  • Disable the IBE feature. The Identity-Based Encryption service is the exposed surface. Turn it off in the GUI under Encryption, IBE, IBE Service, or from the CLI:
config system encryption ibe set status disable end
  • Restrict the management interface. Block access to the FortiMail management GUI from the internet and permit it only from a trusted private network. This is good practice independent of this CVE, and it is the control that would have blunted the attack entirely.

Disabling IBE is not free: it is the feature that lets external recipients retrieve encrypted mail through a web portal, and many organizations enabled it to meet a compliance obligation. Switching it off to dodge a zero-day is a business decision as much as a configuration change, which we cover in Why Disabling a Feature to Dodge a Zero-Day Is a Business Decision.

Because exploitation predates most patches, assume the workaround alone does not clear you. Hunt for the indicators Fortinet published. Verify the SHA-256 hashes of liblog.so, smit, webconsole, and mailservice, inspect /data/etc/ld.so.preload and /data/etc/httpd.conf for tampering, review your archive and admin account configuration for unfamiliar entries, and search logs for connections to 79.141.169.187 and 45.129.0.192. Building a repeatable version of that check is covered in How to Detect Unauthorized File Changes on a Hardened Appliance. If you find artifacts, treat the appliance as fully compromised and follow Fortinet's forensic triage guidance before you rebuild. Our existing guide, How to Check an Email Security Gateway for Compromise After a Zero-Day, walks through the broader containment sequence.

Long-Term Outlook

This is the second mail-server zero-day to draw CISA's attention in recent weeks, following the Zimbra SNMP flaw in August, and it fits a durable pattern: internet-facing management interfaces on security appliances are among the most heavily hunted targets on the network. The lesson is not specific to Fortinet. Any appliance whose administrative GUI faces the internet is one parser bug away from the scenario above. Pull those interfaces behind a VPN or a management network, inventory which of your appliances still expose them, and upgrade to the listed fixed releases, keeping IBE disabled or webmail restricted only until the appliance is on a fixed build. The vendors will keep shipping fixes; the exposure is yours to close before the next advisory lands.

Sources

  • Fortinet PSIRT advisory FG-IR-26-175: https://fortiguard.fortinet.com/psirt/FG-IR-26-175
  • NVD entry for CVE-2026-104286: https://nvd.nist.gov/vuln/detail/CVE-2026-104286
  • CISA Known Exploited Vulnerabilities catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
  • BleepingComputer, "Fortinet warns of critical FortiMail flaw exploited in zero-day attacks": https://www.bleepingcomputer.com/news/security/fortinet-warns-of-critical-fortimail-flaw-exploited-in-zero-day-attacks
  • The Hacker News, "Critical FortiMail Zero-Day Flaw Exploited in Attacks": https://thehackernews.com/2026/10/critical-fortimail-zero-day-flaw.html
  • The Register, "Fortinet sounds the alarm over actively exploited FortiMail zero-day": https://www.theregister.com/security/2026/10/02/fortinet-sounds-the-alarm-over-actively-exploited-fortimail-zero-day/