critical severityConfidence highHistorical record

FortiMail unauthenticated path traversal hits CISA KEV

Direct answer

FortiMail unauthenticated path traversal hits CISA KEV, also tracked as CVE-2026-104286 / FG-IR-26-175 / Fortinet FortiMail Path Traversal Vulnerability is a critical-severity threat campaign HOL Guard tracked from Oct 1, 2026 to Oct 1, 2026, verified against 4 primary sources and last reviewed Oct 1, 2026. Active tracking has ended and the record remains published as a permanent historical research record.

CISA added CVE-2026-104286 to KEV on 2026-10-01 (due 2026-10-04, forensic triage Yes, catalogVersion 2026.10.01). Fortinet FortiMail path traversal (CWE-22) plus NULL-byte neutralization (CWE-158) in the GUI/IBE path: unauthenticated attackers can write arbitrary files over crafted HTTP/HTTPS. Fortinet rates Critical CVSSv3 9.8, Known Exploited Yes, and published IoCs. Workaround: disable IBE or keep management off the public internet. Upcoming fixes: 8.0.2 / 7.6.7 / 7.4.9; 7.2 fleets move to 7.4+.

Also tracked as CVE-2026-104286 · FG-IR-26-175 · Fortinet FortiMail Path Traversal Vulnerability

First observed
Oct 1, 2026
Last observed
Oct 1, 2026
Last reviewed
Oct 1, 2026
Tracking ended
Oct 1, 2026

Uncertainty and limitations

Read the evidence limits before acting on this record.

Fixed builds listed as upcoming at advisory time. NVD analysis empty at publish. Exact exploit request shape not fully public beyond path traversal + NULL byte. Known ransomware campaign use Unknown.

  • Not a FortiGate or other Fortinet product advisory
  • Fixed builds listed as upcoming at FG-IR-26-175 publish time
  • NVD analysis empty at blog publish
  • Known ransomware campaign use Unknown

Guard coverage and policy

What Guard's reviewed assertions do and do not claim for this campaign, and the reviewed starting points for defense.

Covered by Guard

  • provides evidence

    Evidence pack may still show ADP stub title until editorial lands; campaign tracks sources independently.

  • Recipe available

    Disable FortiMail IBE via CLI until patched builds are installed

    Does not replace version upgrade; confirm status with get after change.

Safe next step. Campaign guidance is defensive context. It does not auto-apply policy or claim universal campaign coverage.

Timeline

Reviewed events, oldest first, each tied to a verified source.

  1. Disclosure

    Fortinet published FG-IR-26-175 for CVE-2026-104286 Critical unauth FortiMail path traversal with Known Exploited Yes, IoCs, and IBE disable workaround.

    Source:Fortinet PSIRT FG-IR-26-175

  2. Disclosure

    CISA added CVE-2026-104286 to KEV with dueDate 2026-10-04 and forensic triage Yes (catalogVersion 2026.10.01).

    Source:CISA Known Exploited Vulnerabilities catalog

  3. Update

    HOL Guard published operator write-up and same-day KEV coverage.

    Source:HOL Guard operator write-up

Publication clock: 20.5 hours from reviewed disclosure timestamp to HOL publication; 12-hour critical target; historical backfill outside target.

Reviewed artifacts

The specific artifacts this record concerns, as reviewed. Names and versions are shown as text; a registry link is not recorded here.

  • FortiMail@8.0.0-8.0.1; 7.6.0-7.6.6; 7.4.0-7.4.8; 7.2.0-7.2.9 (upcoming 8.0.2/7.6.7/7.4.9)fortinetpackage

Indicators

Published values are defanged so nothing here is copy-paste executable. These are inert text, never links.

3 indicators are recorded as not defanged. Treat them as live.

  • file hashhigh confidencenot defanged
    8015f34dc84922b03688399d7f9fe7a00361789f7e420c7e2a2cdb23e75cef84
  • file hashhigh confidencenot defanged
    77324ac428bde86d351fc5fc06f6d64a6bfe737dfb2743df1d4c5ac2418a5b6a
  • file hashhigh confidencenot defanged
    8953ec7960b09f544a880b072ad4e6cfda7a8303f486251d3478dcfdfbac23b6

Sources

Every claim on this record is traceable to the sources below.

Campaign questions, answered

CISA added CVE-2026-104286 to KEV on 2026-10-01 (due 2026-10-04, forensic triage Yes, catalogVersion 01). HOL Guard tracked the campaign from Oct 1, 2026 to Oct 1, 2026.

No. Active tracking ended Oct 1, 2026; this page remains as a labeled historical research record and does not imply the threat is currently active.

The record cites 4 primary sources, names 1 reviewed artifact, and was last fully reviewed Oct 1, 2026 by HOL Guard Security Publishing. 3 of its 3 indicators are recorded as not defanged and should be treated as live. Its uncertainty and limitations are stated on the record itself.

Campaign guidance is defensive context. It does not auto-apply policy or claim universal campaign coverage. The campaign-specific policy starting point is linked from the coverage section of this record.

The permalink above is permanent. The full record can be downloaded from this page as JSON, an artifact CSV, and a STIX 2.1 bundle, and corrections can be requested through the published correction path on the record. Fixed builds listed as upcoming at advisory time. NVD analysis empty at publish. Exact exploit request shape not fully public beyond path traversal + NULL byte. Known ransomware campaign use Unknown.

Reviewed in full by HOL Guard Security Publishing.

Published
Last full review
Last modified

Report a correction

Record HGTC-2026-49ACCFCC