CVE-2026-104286: Fortinet FortiMail Path Traversal
Fortinet FortiMail · listed in the CISA catalog of actively exploited vulnerabilities since 2026-10-01.
- CVSS v3.1 (CVE record)
- 9.8
- critical
- EPSS (exploit probability, 30 days)
- 4.6%
- higher than 91.8% of all CVEs
- Added to CISA KEV
- 2026-10-01
- US federal due date 2026-10-04
- Automatable (CISA SSVC)
- yes
- technical impact: total
CVE-2026-104286 explained
CVE-2026-104286 is a critical path traversal vulnerability in Fortinet FortiMail. An unauthenticated attacker can write arbitrary files on the underlying system by sending crafted HTTP or HTTPS requests. CISA lists it as known to be exploited, so exposed FortiMail devices face a serious risk.
Impact
An unauthenticated attacker with network access can write arbitrary files on the FortiMail system. No user interaction is needed and attack complexity is low. Confidentiality, integrity and availability impacts are all high. CISA rates the vulnerability as automatable, so attackers can exploit it at scale. CISA also rates the technical impact as total, meaning full control of the affected device. Attackers are known to exploit it. Ransomware use is unknown.
Who is affected
Fortinet FortiMail versions 7.0.0 through 7.0.9, 7.2.0 through 7.2.9, 7.4.0 through 7.4.8, 7.6.0 through 7.6.6, and 8.0.0 through 8.0.1 are affected. Fixed versions are 7.4.9, 7.6.7 and 8.0.2. Version 7.2.10 is announced as the fix but is not yet released. The CVE record names no fixed version for 7.0.0 through 7.0.9.
Written with AI from the data on this page and checked against it automatically.
Official description
An improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet 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 may allow an unauthenticated attacker to write arbitrary files on the underlying system via crafted HTTP or HTTPS requests.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Fortinet FortiMailAffectedFixed in
- ≥ 7.0.0, ≤ 7.0.9
- ≥ 7.2.0, ≤ 7.2.9
- ≥ 7.4.0, ≤ 7.4.8
- ≥ 7.6.0, ≤ 7.6.6
- ≥ 8.0.0, ≤ 8.0.1
- 7.2.10 (upcoming)
- 7.4.9
- 7.6.7
- 8.0.2
Fixed versions taken from the CNA solution text.
| Product | Affected | Fixed in |
|---|---|---|
| Fortinet FortiMailFixed versions taken from the CNA solution text. |
|
|
How to fix it
- Update to a fixed version: 7.2.10 (upcoming), 7.4.9, 7.6.7, 8.0.2.
- Vendor advisory: fortiguard.fortinet.com/psirt/FG-IR-26-175
- CISA's deadline for US federal agencies: 2026-10-04 (passed) – a useful benchmark for everyone else, too.
What to do
- Upgrade to
8.0.2,7.6.7or7.4.9, depending on your installed release. - If you run
7.2.0through7.2.9, apply vendor mitigations now and upgrade to7.2.10once released, or move to a fixed release. - If you run
7.0.0through7.0.9, follow the Fortinet advisory; the record names no fixed version for these releases. - Restrict HTTP and HTTPS access to FortiMail management interfaces; keep them off the internet.
- Check devices for signs of compromise, such as unexpected files, following CISA's forensics triage requirements.
- If mitigations are unavailable, follow CISA's required action and discontinue use of the product.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-22 Execute unauthorized code or commands
Questions about CVE-2026-104286
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2026-104286 to its Known Exploited Vulnerabilities catalog on 2026-10-01, with a US federal due date of 2026-10-04. Whether it is used in ransomware campaigns is unknown.
- Does an attacker need credentials?
- No. The attack requires no privileges and no user interaction. It works over the network with crafted HTTP or HTTPS requests.
- What should I do if no fixed version is available for my release?
- Apply the mitigations in the Fortinet advisory and limit network exposure. CISA requires discontinuing use of the product if mitigations are unavailable. For
7.2.0through7.2.9,7.2.10is announced as the fix.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.