CVE-2026-104286
Fortinet FortiMail Path Traversal Vulnerability
Description
CVE-2026-104286 is a critical path traversal vulnerability in Fortinet FortiMail that lets an unauthenticated attacker write arbitrary files on the underlying system through crafted HTTP or HTTPS requests. Affected versions are FortiMail 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, 7.4.0 through 7.4.8 and 7.2.0 through 7.2.9. Because FortiMail is a mail security gateway that stands at the perimeter and must accept connections, an arbitrary file write with no credentials is effectively a path to control of the appliance and of the mail flow it inspects. CISA has added CVE-2026-104286 to the Known Exploited Vulnerabilities catalog, its EPSS score of 2.2% ranks it in the 82nd percentile, and its remediation deadline of October 4, 2026 has already passed.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HOpen in CalculatorAffected Products
| Vendor | Product | Version |
|---|---|---|
| fortinet | fortimail | >= 7.0.0, <= 7.0.9; >= 7.2.0, <= 7.2.9; >= 7.4.0, < 7.4.9; >= 7.6.0, < 7.6.7; >= 8.0.0, < 8.0.2 |
References
- https://fortiguard.fortinet.com/psirt/FG-IR-26-175(Mitigation, Vendor Advisory)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-104286(US Government Resource)
Weakness Type
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Path traversal occurs when software builds a file path from external input without neutralizing sequences such as ../ that make the result resolve outside the intended directory. In FortiMail, path components taken from an HTTP or HTTPS request are used to construct a destination for a file write without that constraint, so an attacker can direct the write to any location the web service can reach on the appliance.
Learn more: CWE-22 — Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Impact Analysis
CVE-2026-104286 has a CVSS 3.1 base score of 9.8 (Critical) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Attack Vector (Network), Privileges Required (None), User Interaction (None): a crafted HTTP or HTTPS request is the whole attack — no account, no token, no victim — and FortiMail's web interfaces are reachable wherever administrators or users access the appliance. Attack Complexity (Low): the traversal is deterministic and needs no timing. Confidentiality, Integrity and Availability (all High): NVD scores arbitrary file write as full impact across all three because, on an appliance, choosing the location and content of a file is the standard route to code execution, configuration tampering and service destruction. The consequence for a mail gateway is severe beyond the box itself: it processes every inbound and outbound message, holds TLS certificates and directory credentials, and is trusted by the internal mail infrastructure behind it. With an EPSS score of 2.2% in the 82nd percentile, CISA confirmation of exploitation in the wild, and a deadline that has already passed, an unpatched FortiMail is an incident waiting to be discovered.
Exploit Maturity
CISA has added CVE-2026-104286 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, and the remediation deadline of October 4, 2026 has already passed; the entry does not flag use in ransomware campaigns. The references are the Fortinet PSIRT advisory FG-IR-26-175, which also carries mitigation guidance, and the CISA catalog entry — no public proof-of-concept appears in the reference set. The EPSS score of 2.2% places the vulnerability in the 82nd percentile, well above the median, which is what one expects for an unauthenticated flaw in an internet-facing Fortinet appliance: this product family is scanned continuously, and historically the interval between a Fortinet advisory and broad exploitation attempts has been measured in days. Any FortiMail in the affected ranges that was reachable before patching should be examined for file system changes rather than assumed clean.
Remediation
- Carry out the action CISA requires, immediately. Apply mitigations in accordance with Fortinet's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV remediation deadline of October 4, 2026 has already passed.
- Upgrade FortiMail to a fixed release as listed in Fortinet advisory FG-IR-26-175. Affected ranges are 8.0.0–8.0.1, 7.6.0–7.6.6, 7.4.0–7.4.8 and 7.2.0–7.2.9, so a patch level inside the same minor branch is typically what is required; the advisory also documents the vendor's mitigation options.
- Restrict access to the appliance's HTTP and HTTPS interfaces now. Because the vulnerability is unauthenticated and reached over the web interface, limiting the administrative and webmail interfaces to trusted networks or a VPN removes the attacker's reach while the upgrade is scheduled — and the administrative interface should never be published to the internet in the first place.
- Treat an exposed appliance as compromised and investigate. Review web server logs for requests whose paths contain traversal sequences, look for files in locations that should not have been written to, check for unexpected processes, cron entries and outbound connections, compare the configuration against a known-good backup, and rotate TLS certificates, LDAP or Active Directory bind credentials and API keys the appliance holds.
- Harden path handling and privilege separation. Where you build file-handling code, canonicalize every externally derived path and verify that the resolved absolute path still lies within the permitted directory before writing; validate file names against an allowlist rather than filtering traversal sequences, and run the handling component with the least privilege required so that a successful write does not become a system takeover.
Technical Details
FortiMail's web service derives part of a file system path from data in an HTTP or HTTPS request and uses it in a write operation without properly limiting the result to the restricted directory the operation belongs in — the CWE-22 mechanism. Supplying relative traversal sequences makes the resolved path escape that directory, and because the attacker also controls the content being written, the write can target a location from which the appliance later executes or interprets the file. That is why NVD rates the confidentiality, integrity and availability impact as High even though the described primitive is only a write: on an appliance, an attacker-chosen write is the standard precursor to code execution. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H states the attack conditions plainly — remote, trivial, unauthenticated, no interaction — with an unchanged scope, since the impacted authority is the FortiMail appliance itself. In deployment terms, however, that appliance is the organization's mail perimeter, so the practical reach extends to everything flowing through it.
Frequently Asked Questions
Is CVE-2026-104286 being actively exploited?
Yes. CISA has added CVE-2026-104286 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, and the remediation deadline of October 4, 2026 has already passed. The EPSS score of 2.2% places the vulnerability in the 82nd percentile for exploitation likelihood, and use in ransomware campaigns is not recorded in the KEV entry.
What products are affected by CVE-2026-104286?
CVE-2026-104286 affects Fortinet FortiMail versions 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, 7.4.0 through 7.4.8 and 7.2.0 through 7.2.9. FortiMail is Fortinet's mail security gateway, deployed as a hardware appliance, virtual machine or hosted instance; all form factors running an affected version are in scope.
How do I fix CVE-2026-104286?
Upgrade FortiMail to a fixed release for your branch as listed in Fortinet advisory FG-IR-26-175. Until the upgrade is complete, restrict the appliance's HTTP and HTTPS interfaces to trusted networks, since the vulnerability requires no authentication. Afterwards, check the file system for files written outside expected locations and rotate the certificates and directory credentials the appliance stores.
How severe is CVE-2026-104286?
CVE-2026-104286 is rated Critical with a CVSS 3.1 base score of 9.8: an unauthenticated remote attacker can write arbitrary files without any user interaction, which on an appliance leads to code execution and full compromise. Its EPSS score of 2.2% sits in the 82nd percentile. Because FortiMail inspects all of an organization's email and holds the credentials for doing so, the operational severity goes beyond the appliance itself.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.