Threat watch Email security / incident response
FortiMail under active exploitation: mitigation is not incident closure.
A pre-authentication file-write flaw turns the mail gateway itself into the response priority. Closing the exposed path and determining what happened before it closed are separate jobs.
- Vulnerability
- CVE-2026-104286
FortiMail · FG-IR-26-175 - Severity
- 9.8 / Critical
No authentication required - Exploitation
- Reported in the wild
KEV added October 1
Sources: Fortinet PSIRT and CISA KEV. Release status below reflects the advisory, not an authenticated download-portal check.
A file-write flaw, before a successful login
Fortinet identifies path traversal and improper NULL-character handling in FortiMail. Crafted HTTP or HTTPS requests can write arbitrary files on the underlying system without authentication; the vendor lists unauthorized code or command execution as the impact. The public advisory does not disclose the exact parser sequence or a complete exploit chain. Read the vendor advisory.
- 01 · Entry
Unauthenticated web request
HTTP/S reaches a vulnerable FortiMail service.
A failed-login alert is not a prerequisite. - 02 · Failure
Arbitrary file write
Path and NULL-character handling fail to constrain the operation.
The integrity of the appliance is now in question. - 03 · Reported impact
Code or command execution
Fortinet identifies this consequence; each deployment still needs investigation.
Exposure alone does not prove compromise.
The IBE-related mitigations identify where to reduce exposure. They do not establish whether an earlier intrusion has left persistence behind.
For an industrial operator, this is an IT dependency issue, not a PLC vulnerability. Ask what the mail appliance can reach, which integrations it uses, and which operational workflows depend on it. A business-side compromise becomes an OT concern through real trust relationships, not simply because the organization runs a plant.
Two jobs, with different evidence of completion
Exposure reduction
Can an untrusted requester still reach it?
Apply the appropriate vendor workaround, verify the intended restriction, and prepare the supported upgrade.
Keep: change record + exposure checkCompromise assessment
What happened before the restriction?
Preserve logs and available artifacts, compare configuration changes, and investigate suspicious activity.
Keep: evidence + timeline + dispositionCoordinate the two efforts. Preserve evidence before disruptive changes when possible; do not turn “finish the investigation first” into a reason to leave active exposure unmanaged.
CISA's triage guidance emphasizes preservation, coordinated containment, and an explicit escalation decision. Our practical recommendation is to name an owner for each job. Record what could not be collected and why, rather than treating missing telemetry as a clean bill of health.
Confirm the branch, then choose a workable mitigation
| Branch | Affected versions | Vendor-listed solution |
|---|---|---|
| 8.0 | 8.0.0 through 8.0.1 | 8.0.2 or later, listed as upcoming |
| 7.6 | 7.6.0 through 7.6.6 | 7.6.7 or later, listed as upcoming |
| 7.4 | 7.4.0 through 7.4.8 | 7.4.9 or later, listed as upcoming |
| 7.2 | 7.2.0 through 7.2.9 | Migrate to branch 7.4 or later; select a fixed release |
Use the current advisory and vendor-supported upgrade path. Moving to an affected 7.4 release is not remediation. For versions outside this table, confirm status with Fortinet rather than assuming they are safe.
The advisory offers three mitigation paths:
- Disable Identity-Based Encryption (IBE). In the GUI, set the IBE service off under Encryption → IBE. Fortinet also provides the CLI below. Plan for the impact on encrypted-message workflows.
- Restrict webmail reachability. Remove Internet access to the FortiMail webmail interface, or limit access to a trusted private network. Restricting only management access is not the same change.
- Use the vendor-specified WAF filter where a WAF fronts FortiMail. Block POST requests to
/ibecontaining../. Confirm that the intended traffic actually traverses the enforcement point; do not substitute an untested rule or treat blocked requests as proof the host is clean.
config system encryption ibe
set status disable
end
Commands and alternatives: Fortinet PSIRT workaround. Confirm service dependencies and change authority before applying them. Recheck the advisory for released fixes and revised instructions.
Look beyond a traversal signature
A blocked request answers a narrow question: the control handled that request. To investigate prior activity, correlate available webmail/WAF records, appliance event and encryption logs, configuration history, and outbound network telemetry.
Vendor indicators · system activity
Unexpected execution and administration
The current advisory includes cron activity involving /migadmin, an admin logout with ui=(null), and creation of an archive234 remote archive account using /uploads.
Vendor indicators · encryption activity
IBE errors and login failures
Fortinet lists an invalid-Base64 exception in IBE processing and internal-user login failures. Preserve the full event context; an error alone does not establish exploitation.
The advisory also lists 79[.]141.169.187 and 45[.]129.0.192. Search retained telemetry for the current vendor indicators and exact log patterns. An absence of these indicators is not evidence that no other infrastructure or technique was used.
For suspicious appliances, involve the incident-response lead and Fortinet support. Assess persistence, configuration integrity, and access to connected systems. Determine which credentials or secrets could have been exposed, then coordinate their replacement from trusted systems with containment and recovery. Patching the entry point does not automatically remove prior persistence.
Verify that the exposed path is closed. Then document what the evidence says about the appliance behind it.
Sources and scope
- Fortinet PSIRT FG-IR-26-175: affected releases, impact, workarounds, indicators, and release status.
- CISA KEV and its official machine-readable catalog: October 1 addition, October 4 catalog date, and forensic-triage flag.
- BOD 26-04 and implementation guidance: federal applicability, asset-based deadlines, preservation, and triage.
Our research fleet includes Fortinet appliance decoys, not a FortiMail implementation. The audited material reviewed for this article does not establish exploitation of CVE-2026-104286; we have not used unrelated Fortinet traffic as corroboration.