Skip to main content
VulnerabilityPublished Updated

CVE-2026-104286: Fortinet FortiMail · Execute Unauthorized Code or Commands

Affects Fortinet FortiMailSource CVE Database V5

0
Compare

Exploited in the wild · KEV due 4 Oct 2026 · public exploit available · 4% EPSS · patch available : patch Fortinet FortiMail now.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (fortinet)CVSS 3.19.8
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
EPSS
4.5% chance of exploitation in 30 days – higher than 91% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 1 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: evidence found.

    Listed in CISA KEV the same day as disclosure

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Fortinet, Inc.

    , 5 minutes before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 24 minutes after disclosure

  4. , the same day as disclosure

  5. KEV remediation due

    US federal deadline

    , 3 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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.

Affected software

ProductAffectedFixed in
FortinetFortiMailAffected
  • >=8.0.0 <=8.0.1
  • >=7.6.0 <=7.6.6
  • >=7.4.0 <=7.4.8
  • >=7.2.0 <=7.2.9
  • >=7.0.0 <=7.0.9
Fixed in–
Mavenfortinet/fortimailpkg:maven/fortinet/fortimailOther threatsAffected
  • =8.0.0
  • >=7.6.0 <=7.6.5
  • >=7.4.0 <=7.4.6
  • >=7.2.0 <=7.2.9
  • >=7.0.0 <=7.0.9
Fixed in–

CPE configurations (38)

  • cpe:2.3:a:fortinet:fortimail:8.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortimail:8.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortimail:7.6.6:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortimail:7.6.5:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortimail:7.6.4:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortimail:7.6.3:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…