Advisory

CVE-2026-104286 (CVSS 9.8): Critical Path Traversal in Fortinet FortiMail Enables Unauthenticated File Write

A critical path traversal vulnerability (CWE-22) in Fortinet FortiMail allows an unauthenticated remote attacker to write arbitrary files to the underlying system via crafted HTTP or HTTPS requests. The flaw carries a CVSS 3.1 score of 9.8 and has been added to the CISA Known Exploited Vulnerabilities catalog, indicating active exploitation in the wild.

TL;DR: Organizations running FortiMail 7.0 through 8.0.1 must apply Fortinet's vendor-issued patches immediately and follow CISA BOD 26-04 remediation timelines. If patching is not immediately possible, assess internet exposure and implement compensating controls as directed by Fortinet and CISA.

What Is the Vulnerability?

CVE-2026-104286 is a path traversal vulnerability (classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory) affecting multiple versions of Fortinet FortiMail. The vulnerability arises from insufficient validation of file path inputs, allowing an attacker to reference locations outside the intended restricted directory on the underlying filesystem.

According to the NVD description and the CISA KEV catalog entry, the flaw also involves improper neutralization of NULL byte or NULL character sequences, which attackers can leverage to bypass path-restriction logic built into the application.

The attack is conducted via crafted HTTP or HTTPS requests and requires no authentication, no special privileges, and no user interaction. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects the full triad of Confidentiality, Integrity, and Availability impact at HIGH, yielding a Critical score of 9.8 out of 10.0.

The core danger is arbitrary file write: a successful attacker can place files of their choosing anywhere the FortiMail process has write access on the host operating system. This capability is frequently a prerequisite for achieving remote code execution or persistent backdoor access on the affected appliance.

Who and What Is Affected?

The following Fortinet FortiMail version ranges are confirmed as vulnerable per the NVD advisory:

  • FortiMail 8.0.0 through 8.0.1
  • FortiMail 7.6.0 through 7.6.6
  • FortiMail 7.4.0 through 7.4.8
  • FortiMail 7.2.0 through 7.2.9
  • FortiMail 7.0 — all versions

FortiMail is a dedicated email security gateway product widely deployed by enterprises, government agencies, and managed service providers to filter spam, malware, and phishing content. Instances that are internet-exposed — particularly those handling inbound mail delivery on public IP addresses — represent the highest-risk attack surface for this vulnerability, since the attack vector is network-based with no authentication requirement.

Even FortiMail appliances placed behind perimeter firewalls should be treated as at risk if any path exists for external actors to reach their management or mail-processing interfaces.

What Is the Potential Impact?

The CVSS score of 9.8 (Critical) reflects the worst-case outcome across all three impact dimensions:

  • Integrity (HIGH): An unauthenticated attacker can write arbitrary files to the system. This includes the ability to overwrite configuration files, drop web shells, or plant malicious scripts that execute with the privileges of the FortiMail service process.
  • Confidentiality (HIGH): Depending on what files are written and where, an attacker could stage subsequent operations — such as reading sensitive mail data, credentials stored on the appliance, or private keys — after establishing a foothold.
  • Availability (HIGH): Overwriting critical system or application files can render the FortiMail appliance inoperable, disrupting inbound and outbound mail flow for the affected organization.

Because this is a pre-authentication, network-reachable vulnerability, no prior access to the target environment is required. The low attack complexity rating means exploitation does not depend on race conditions, special environmental factors, or user-triggered events.

CISA has added this CVE to the Known Exploited Vulnerabilities (KEV) catalog (added 2026-10-01), confirming that exploitation has been observed. Organizations should treat this as an actively weaponized vulnerability and prioritize remediation accordingly.

What Should You Do Right Now?

CISA's required action for this KEV entry is clear: "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 guidance." The following steps are recommended:

  1. Identify all FortiMail instances in your environment. Confirm version numbers for every deployment, including virtual appliances and cloud-hosted instances.
  2. Apply Fortinet's official patches as directed in Fortinet's own security advisory for CVE-2026-104286. Consult Fortinet's PSIRT page for the authoritative patch guidance.
  3. Follow BOD 26-04 timelines. US Federal Civilian Executive Branch (FCEB) agencies are bound by BOD 26-04 patch deadlines. All other organizations should treat KEV entries as high-priority regardless of regulatory obligation.
  4. Restrict internet exposure of FortiMail management interfaces where operationally possible while patching is underway. FortiMail appliances that do not need to be directly reachable from the public internet for mail delivery should not be.
  5. Conduct forensic triage per CISA's "Forensics Triage Requirements" referenced in the KEV entry if you suspect your systems may already be compromised. Look for unexpected files, modified configurations, or anomalous process activity on affected appliances.
  6. Discontinue use of unpatched instances if no mitigations can be applied, as directed by CISA BOD 26-04 guidance for situations where vendor mitigations are unavailable.

Primary references: CISA KEV Catalog | NVD Entry for CVE-2026-104286 | Fortinet PSIRT

How Continuous External Testing Surfaces This Exposure

One of the most dangerous characteristics of CVE-2026-104286 is that it is exploitable before any credential is presented — meaning the window between a vulnerable appliance going live (or remaining unpatched) and potential compromise can be extremely short once a vulnerability becomes public knowledge and enters the KEV catalog.

Continuous external attack surface monitoring helps organizations in several key ways against vulnerabilities like this one:

  • Asset discovery: Automated external scanning identifies FortiMail instances reachable from the internet — including forgotten or shadow-IT deployments that internal teams may not know are exposed.
  • Version fingerprinting: Network and host-level probes can identify service banners and other indicators that correlate to vulnerable version ranges, flagging at-risk appliances before an attacker finds them first.
  • Exposure validation: Confirming whether the vulnerable HTTP/HTTPS endpoints are actually reachable from outside the perimeter — not just theoretically exposed — allows security teams to prioritize remediation efforts accurately.
  • Change detection: When new assets are added or configurations change (for example, a firewall rule inadvertently exposes a FortiMail management port), continuous scanning surfaces the new exposure in near-real time rather than at the next scheduled audit cycle.

For a pre-auth, network-exploitable vulnerability rated CVSS 9.8 and confirmed in the KEV catalog, the time between patch availability and active exploitation attempts against unpatched systems can be measured in hours. Continuous external testing compresses the detection window so that your remediation actions are informed by current, ground-truth visibility into what attackers can actually see and reach.

Sources & further reading: NVD CVE-2026-104286 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: fortiguard.fortinet.com, cisa.gov. This advisory contains no exploit code.

Frequently asked questions

Is CVE-2026-104286 being actively exploited?

Yes. CISA added CVE-2026-104286 to the Known Exploited Vulnerabilities (KEV) catalog on 2026-10-01, which confirms that exploitation has been observed in the wild. Organizations should treat remediation as urgent.

Do I need to be authenticated to be at risk from this vulnerability?

No. The vulnerability can be exploited by an unauthenticated attacker over the network via crafted HTTP or HTTPS requests. No credentials, no user interaction, and no elevated privileges are required, which is reflected in the CVSS 3.1 vector (PR:N/UI:N/AC:L).

Which versions of FortiMail are affected?

According to the NVD advisory, the affected versions are: FortiMail 8.0.0 through 8.0.1, FortiMail 7.6.0 through 7.6.6, FortiMail 7.4.0 through 7.4.8, FortiMail 7.2.0 through 7.2.9, and all versions of FortiMail 7.0. Consult Fortinet's official PSIRT advisory for the definitive list of fixed versions.

What if I cannot patch immediately — what compensating controls are available?

CISA's required action directs organizations to follow Fortinet's vendor instructions for mitigations. If mitigations are unavailable, CISA BOD 26-04 guidance states organizations should discontinue use of the product. As a general compensating control, restricting public internet access to FortiMail's HTTP/HTTPS interfaces reduces the attack surface while patching is arranged. Contact Fortinet support directly for appliance-specific guidance.