Skip to content
Reachability Analysis

CVE-2026-104286: Fortinet FortiMail, is it exploitable where you run it

Code called: openReached: yesControl in front: noExploitation known: yesWalk it through the four questions

What the flaw is

FortiMail has a path traversal flaw (CWE-22) combined with improper handling of a NULL byte (CWE-158) in its web interface. By sending crafted HTTP or HTTPS requests, an unauthenticated attacker can write arbitrary files on the underlying system. Fortinet lists the impact as execution of unauthorized code or commands, and rates it 9.8 (CVSS base score; temporal 8.8). Fortinet's workaround and its log lines tie the flaw to the IBE service.

Writing files on a mail gateway can lead to code running as root. The indicators Fortinet publishes show what attackers did after that: a cron job run by root, an admin session logged out for no clear reason, and a new mail archive account that sends archived mail to an outside server by remote copy. That last step would give an attacker a copy of mail passing through the appliance.

Fortinet's own Product Security team found the flaw.

Are you exposed: each condition and how to check it

Condition for exposureHow to check it on your system
self-managed FortiMail (not FortiMail Cloud) runs an affected releaseIn the CLI run get system status and read the Version line. In the GUI open Dashboard > Status and read System Information. Compare with the versions table. On a FortiMail Cloud instance the same command should report 7.6.7 GA or 8.0.2 GA.
the IBE service is enabled (inferred from Fortinet's workaround and log lines; the advisory does not state it as a condition) and the web interface is reachable by the attackerIBE: in the GUI open Encryption > IBE and read IBE Service; in the CLI run show system encryption ibe (or show full-configuration system encryption ibe to include defaults) and look for set status enable. Reachability: run show system interface and read set allowaccess on each interface for http and https, then from outside the trusted network test with nc -vz 443 (and 80). Review firewall and NAT rules that publish the appliance, including webmail and the IBE portal.

Affected and fixed versions

NVD's product list shows 7.0.0 through 7.0.9, while Fortinet's advisory says all 7.0 versions are affected. Use Fortinet's statement.
FortiMail trainAffectedFirst fixed release
8.08.0.0 through 8.0.18.0.2
7.67.6.0 through 7.6.67.6.7
7.47.4.0 through 7.4.87.4.9
7.27.2.0 through 7.2.97.2.10 (listed as upcoming in the advisory revision of 7 Oct 2026)
7.0All versionsNo fixed 7.0 release; migrate to a fixed release
FortiMail CloudAll firmware before 5 Oct 2026Fixed by Fortinet on 5 Oct 2026 by updating every system to 7.6.7 GA or 8.0.2 GA; no customer action

If the fix cannot go in yet

  • Turn off the IBE service. In the GUI: Encryption > IBE > IBE Service set to off. In the CLI: config system encryption ibe, then set status disable, then end. Cost: IBE secure mail stops working. Recipients can no longer open or reply to IBE-encrypted messages through the FortiMail secure portal, and users who depend on IBE policies lose that delivery path.
  • Or block internet access to the FortiMail webmail interface and allow it only from trusted private networks. Cost: external users, including IBE recipients, lose access to webmail and the secure portal.
  • Or, if a web application firewall sits in front of FortiMail, block POST requests to /ibe whose content contains a parent-directory sequence (../). Cost: the rule has to be written and tested on your WAF.
  • Fortinet urges customers who cannot upgrade to apply one of these workarounds because exploitation is reported.

What to look for

  • Look for signs that the appliance is already compromised before and after patching. Indicator addresses published by Fortinet: 79[.]141[.]169[.]187 and 45[.]129[.]0[.]192. Search firewall and proxy logs for connections to them, and in the GUI check the Archive account settings for entries you did not create (archive234 in Fortinet's example).
  • System event log (Log > Event > System) lines Fortinet lists: a cron entry run as root, shown as type=event subtype=system pri=debug user=system ui=cron msg="(root) CMD (/bin/sh -c 'O=/migadmin ..."; an admin logout with an unknown reason, type=kevent subtype=admin pri=information user=admin ui=(null) action=logout status=success reason=unknown msg="User admin logged out from (null)."; and a configuration entry that adds an archive account with a remote destination, type=kevent subtype=config ... msg="Added 'archive234' to 'archive account'" with rotation-size[50] rotation-time[1] rotation-hour[14] destination[remote] remote-ip[79[.]141[.]169[.]187] remote-username[archive234] remote-directory[/uploads] (user: admin, from: cli).
  • Encryption log (Log > Encryption) lines Fortinet lists: FortiMail::IBE::DecrypterMediaIn constructor entries that read "Caught BufferException(2), BufferImpl.cpp:973, 'Invalid Base64 Encoding at pos 0. Character=0x2a'", followed by "Internal user *@domain.tld failed to log in.".
  • CISA's KEV entry marks forensic triage as Yes for this CVE: preserve the appliance logs and a configuration backup before you change the appliance.

The earliest dated mark of exploitation is CISA's, on 1 Oct 2026, the day of disclosure; exploitation may have begun earlier.

Exploitation reported so far

The advisory names no reporter of the attacks and no date for the first one, and Fortinet has not said how many appliances were hit. KEV lists ransomware campaign use as Unknown.

Why static reachability settles it

Exposure needs an affected FortiMail build, the IBE service on, and a web interface the attacker can reach. A version read, an IBE setting read and a reachability test answer all three on each appliance. Fortinet and CISA confirm active use, so any appliance that passes all three checks should be treated as possibly compromised and checked against the log indicators. See static reachability for what the method proves and misses.

Sources

  1. CVE-2026-104286: NVD record, read 19 Nov 2026
  2. CVE-2026-104286: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
  3. CVE-2026-104286: Fortinet PSIRT advisory FG-IR-26-175 (vendor advisory), read 19 Nov 2026
  4. CVE-2026-104286: Fortinet PSIRT advisory FG-IR-26-175 in CVRF form (revision history), read 19 Nov 2026
  5. CVE-2026-104286: FortiMail CLI reference, system encryption ibe, read 19 Nov 2026

Last reviewed 19 Nov 2026.