Unauthenticated arbitrary file write in Fortinet FortiMail IBE
CVE-2026-104286 is a path traversal vulnerability combined with improper NULL-byte neutralization in the Identity-Based Encryption (IBE) functionality of the Fortinet FortiMail web interface. Improper pathname handling allows an unauthenticated remote attacker to submit crafted HTTP or HTTPS requests and write arbitrary files outside the intended directory on the underlying system, potentially enabling unauthorized code or command execution. Affected versions include FortiMail 8.0.0–8.0.1, 7.6.0–7.6.6, 7.4.0–7.4.8, 7.2.0–7.2.9, and all 7.0 releases. The vulnerability has a CVSS score of 9.8 and has been exploited in the wild.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Arbitrary file writes compromise appliance integrity and can enable configuration tampering, malicious code placement, persistence, and potentially remote code execution or complete appliance takeover. Subsequent compromise could expose email transiting the gateway, archived messages where available, credentials, and cryptographic key material. Attackers could also disrupt email-security services or use the appliance as a foothold for lateral movement. These downstream consequences depend on the files writable and the appliance configuration; they are not established for every observed intrusion.
If you can’t patch tonight, do this now.
Disable Identity-Based Encryption through the GUI under Encryption > IBE > IBE Service, or through the CLI using 'config system encryption ibe', 'set status disable', and 'end'. Alternatively, disable internet access to the webmail interface or restrict it to trusted private networks. Where a WAF protects FortiMail, block POST requests to IBE endpoints containing directory-traversal sequences. Review unexpected files, configuration changes, unauthorized accounts or archiving policies, abnormal scheduled tasks, and unusual outbound connections. These measures reduce exposure but do not replace upgrading or establish that an appliance is uncompromised.
Patch, then assume compromise.
Upgrade FortiMail 8.0 deployments to 8.0.2 or later, 7.6 deployments to 7.6.7 or later, and 7.4 deployments to 7.4.9 or later. Migrate affected 7.2 and 7.0 installations to a supported, fixed release on the 7.4 branch or later. Verify the running firmware after upgrading. Investigate previously exposed appliances for compromise, preserving logs and forensic artifacts before disruptive changes. If compromised, rebuild or restore from a trusted baseline, remove unauthorized configurations and persistence, and rotate potentially exposed credentials, tokens, certificates, and keys. Updating firmware alone does not remove existing attacker access.
1 exploit validated by Mallory's analysis. Hidden: 7 rejected by Mallory's analysis as not a working exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
273 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.