Exploited now
Remediation guideCVE-2026-104286
Improper limitation of a pathname to a restricted directory
- CISA KEV
- Known exploitedadded 1 Oct 2026; US federal deadline 4 Oct 2026
- Exploit likelihood
- 4.6%92nd percentile · FIRST EPSS, 2026-11-15
- Severity
- 9.8 CriticalCVSS 3, Fortinet
- Last verified
- 30 Oct 2026against the sources below
1In plain language
A path traversal and NULL byte flaw in FortiMail may let an attacker who hasn't logged in write arbitrary files on the underlying system, through crafted HTTP or HTTPS requests.
Fortinet says it has been reported to be exploited in the wild and urges customers to apply the workaround below; CISA lists it as known to be exploited.
Fortinet rates the impact as executing unauthorized code or commands. It lists the affected component as the GUI, and has no virtual patch for it.
2Am I affected?
Fortinet's table below lists, for each FortiMail branch, the affected versions and the solution.
FortiMail Cloud: Fortinet remediated it on 5 October 2026 by updating all firmware to 7.6.7 GA or 8.0.2 GA, so FortiMail Cloud customers don't need to do anything.
Affected releases are summarised by release train in the Fix table.
Check your version
A command to show the running version: Not stated by vendor.
3Fix
For 7.2, Fortinet's solution is an upcoming release, 7.2.10 or above. For 7.0 (all versions affected), Fortinet says to migrate to a fixed release.
Until 7.2.10 is out, the workaround and alternatives below are the only protection Fortinet gives for 7.2. our analysis
| Version | Affected | Solution |
|---|---|---|
| FortiMail 8.0 | 8.0.0 through 8.0.1 | Upgrade to 8.0.2 or above |
| FortiMail 7.6 | 7.6.0 through 7.6.6 | Upgrade to 7.6.7 or above |
| FortiMail 7.4 | 7.4.0 through 7.4.8 | Upgrade to 7.4.9 or above |
| FortiMail 7.2 | 7.2.0 through 7.2.9 | Upgrade to upcoming 7.2.10 or above |
| FortiMail 7.0 | 7.0 all versions | Migrate to a fixed release |
4Can't patch tonight?
Fortinet's workaround: disable IBE feature support, in the GUI under Encryption -> IBE -> IBE Service 'off', or at the CLI:
config system encryption ibe set status disable end
Lines to look for in the running configuration, as the vendor shows them.
Alternatively, Fortinet says: disable access to the FortiMail webmail interface from the internet, or limit it to a trusted private network; or, if a Web Application Firewall sits in front of FortiMail, block POST requests to /ibe that contain '../'.
Fortinet doesn't say what disabling IBE does to users who rely on it; plan for that before turning it off. our analysis
5Was I hit?
Fortinet publishes indicators of compromise: IP addresses, system event log entries and encryption log entries. See the advisory for the current list; we link it rather than copy it. Source ↗
What to do if you find a match: Not stated by vendor.
CISA's catalog flags this CVE for forensic triage, and its required action points to CISA's BOD 26-04 guidance and its Forensics Triage Requirements. Source ↗
6Sources
- Improper limitation of a pathname to a restricted directoryFortinet · primary source
- Known Exploited Vulnerabilities catalog: CVE-2026-104286CISA
- CVE-2026-104286NVD
- Exploit Prediction Scoring System (EPSS)FIRST · exploit likelihood, updated daily
Summary of public vendor guidance. Verify against the vendor advisory before acting.
See CVE-2026-104286 in the exploited-now list (exploit likelihood, CISA's description, deadline).
More Fortinet guides
- CVE-2025-25249FortiOS cw_acd heap buffer overflow
- CVE-2025-61624FortiOS CLI path traversal
- CVE-2025-68686FortiOS SSL-VPN symlink patch bypass
- CVE-2026-25089FortiSandbox web UI command injection
- CVE-2026-39808FortiSandbox API command injection