FortiMail Path Traversal Flaw Exploited to Write Arbitrary Files
CVE-2026-104286 lets unauthenticated attackers write arbitrary files on Fortinet FortiMail systems through crafted web requests. It scores 9.8, and CISA listed it as exploited on day one.
TL;DR
- CVE-2026-104286, a path traversal flaw in Fortinet FortiMail, may let an unauthenticated attacker write arbitrary files on the system through crafted HTTP or HTTPS requests [^1].
- It scores 9.8 under CVSS 3.1, and CISA added it to its Known Exploited Vulnerabilities catalog on October 1, the day NVD published it [^1].
Background
FortiMail is Fortinet's email security gateway, which filters an organization's mail for spam and malware. A path traversal flaw lets an attacker escape the directory a program is meant to stay in, often by putting sequences like "../" into a file path. CISA's Known Exploited Vulnerabilities (KEV) catalog lists flaws with confirmed exploitation in the wild [^1].
What happened
According to NVD, an improper limitation of a pathname to a restricted directory (CWE-22) in FortiMail may allow an unauthenticated attacker to write arbitrary files on the underlying system via crafted HTTP or HTTPS requests [^1]. Affected are FortiMail 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, 7.4.0 through 7.4.8, 7.2.0 through 7.2.9, and all versions of 7.0 [^1].
The flaw scores 9.8, critical, under CVSS 3.1 [^1]. NVD published it on October 1, CISA listed it as exploited the same day, and federal agencies had until October 4 to act [^1].
Why it matters
Writing arbitrary files without logging in is often the first step to full control: an attacker who can drop a file where the system will execute or load it can turn file access into code execution. An email gateway is an especially sensitive place for that, because all of an organization's mail passes through it. Every 7.0 release is affected, so older appliances need an upgrade path, not just a patch.
Practical example
Say your company filters its mail with a FortiMail appliance on a 7.4 release between 7.4.0 and 7.4.8, the affected range [^1], and because no login is required, anyone who can reach its web interface could write files to it. Moving to a fixed release and restricting access to the management interface are the immediate steps; given confirmed exploitation, checking for unexpected files belongs on the list too.
Related gear
We recommend this guide because it provides clear, step-by-step explanations of directory traversal and input validation vulnerabilities, helping you understand how attackers exploit flaws like the one found in FortiMail.