External risk intelligence

Fortinet FortiMail Path Traversal Arbitrary File Write Vulnerability

CVE advisoryKnown Exploit

CVE-2026-104286

FortiMail is an email security gateway product designed to be deployed at the network edge to inspect incoming and outgoing mail traffic. It is intended to be internet-facing to perform its primary function, and the vulnerability is reachable via unauthenticated HTTP or HTTPS requests.

Path Traversal

Fortinet Fortimail

7.2.0 to 7.4.87.6.0 to 7.6.68.0.0 to 8.0.1

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability in Fortinet FortiMail allows unauthenticated attackers to write arbitrary files to the system, potentially leading to a compromise. This issue stems from an improper limitation of file paths, enabling attackers to bypass security controls through crafted network requests.

  • Attackers can write files anywhere on the system.
  • Exposure to unauthenticated network requests is a concern.
  • Confirm relevance and assess potential exposure.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can exploit this vulnerability by sending specially crafted requests over HTTP or HTTPS to the FortiMail device. This allows them to write arbitrary files to the system, potentially leading to unauthorized access or modification of sensitive data.

  • No authentication required.
  • Crafted HTTP or HTTPS requests.
  • Arbitrary file write on system.

Live Threat

Current exploitation, exposure, and threat context

An improper limitation of a pathname vulnerability could allow an unauthenticated attacker to write arbitrary files to the underlying system of affected FortiMail devices when they are accessible via HTTP or HTTPS.

  • Arbitrary file writes to system.
  • Via crafted network requests.
  • System compromise or data corruption.

Operational Fix

Recommended remediation, mitigation, and detection steps

Given the critical nature of this vulnerability, Infrastructure and Platform teams are likely responsible for managing FortiMail deployments. The immediate priority is to identify all instances of the affected technology, determine their exposure and business criticality, and locate the accountable system owner. Remediation planning should then proceed based on this risk assessment.

  • Identify all affected FortiMail systems.
  • Verify network exposure and business criticality.
  • Plan and execute vendor-recommended remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Fortinet FortiMail?

FortiMail is an email security gateway engineered to protect organizations by filtering incoming and outgoing email traffic. It typically sits at the network edge to inspect communications for threats like spam, malware, and phishing. Because it serves as a frontline defense for messaging, it is designed to handle high volumes of traffic and is frequently deployed in positions where it must be accessible to outside mail servers.

What does CVE-2026-104286 mean?

This CVE identifies a Path Traversal vulnerability, classified as CWE-22. In plain terms, the software fails to properly check where a file is being saved when it processes specific incoming requests. An attacker can manipulate file paths to write data to locations on the system where they should not have access. Because this bypasses standard file-handling security, it is considered a critical weakness that can lead to full system compromise.

How do attackers trigger this vulnerability?

An attacker triggers this flaw by sending a specially crafted HTTP or HTTPS request to an affected FortiMail device. Because the vulnerability does not require any user credentials or login, it is reachable by anyone who can reach the device over the network. Simply browsing the web interface or sending standard, non-malicious emails does not trigger this issue; the request must be specifically engineered to exploit the path traversal limitation.

Is my organization at risk from CVE-2026-104286?

Your risk level is heavily influenced by how your device is deployed. According to Halo Surface Signal, FortiMail is intended to be internet-facing to perform its core function of inspecting mail traffic. If your specific instance is exposed to the internet, it is directly reachable for these types of malicious requests. Systems tucked away on internal segments without external access have a lower immediate risk, but should still be evaluated.

What should I do if I run FortiMail?

Start by identifying all instances of FortiMail within your environment to see if they fall within the affected version ranges. Once you have a list of assets, check their current version and network connectivity status. Your primary goal is to determine which systems are exposed and identify the team responsible for their upkeep. Prioritize these systems for vendor-recommended updates or guidance, as this vulnerability allows for unauthorized file writes on your infrastructure.

References