Offline FortiMail evidence checker for CVE-2026-104286. FortiMail version and deployment evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads.
Fortinet FortiMail: Path traversal / NULL-byte arbitrary file write
CVE-2026-104286 · offline version assessment · exploitability never tested
fortimail-cve-2026-104286-check is the dedicated repository for CVE-2026-104286, by CompleteTech LLC. It is a standalone, standard-library-only Python 3.10+ checker that compares an operator-supplied FortiMail firmware version with the vendor's dated table of affected and fixed releases. It follows the conventions of node2shell-check and php2shell-check.
The vendor reports this flaw as exploited in the wild, so treat any potentially_affected result as a prompt to verify the appliance promptly.
This tool is version-only and fully offline. The advisory is decided by firmware version, so there is deliberately no network mode: the tool never contacts an appliance, runs no payload, and cannot see the deployed firmware. It reads only the files you name.
not_tested.[!IMPORTANT] A version string is evidence, not verified runtime state. Vendor backports, custom builds, and appliance configuration are not visible to this tool, and exploitability is never tested.
Run from a checkout of this repository:
# One reported version, CSV to stdout (the default format)
python fortimail_cve_2026_104286_check.py --fortimail-version 7.4.8
# The synthetic example inventory, as an HTML report
python fortimail_cve_2026_104286_check.py --inventory inventory.example.json --format html --output report.html
# Your own CSV list (see Inputs), as JSON, exiting 1 if any result is potentially_affected
python fortimail_cve_2026_104286_check.py --list appliances.csv --format json --output assessment.json --fail-on-finding
Supply the plain release number (for example 7.4.8). Build-qualified firmware strings such as v7.4.9,build0123,... are not parsed and give unknown; extract the release number yourself and confirm it on the appliance.
Source: Fortinet PSIRT FG-IR-26-175 (updated 2026-10-07), reviewed 2026-10-24. The rule table is a dated snapshot; recheck the advisory before relying on it.
| FortiMail branch | 8.0 | 7.6 | 7.4 | 7.2 | 7.0 |
|---|---|---|---|---|---|
| Affected | 8.0.0-8.0.1 | 7.6.0-7.6.6 | 7.4.0-7.4.8 | 7.2.0-7.2.9 | sources conflict |
| Fixed in | 8.0.2 | 7.6.7 | 7.4.9 | none; migrate to a fixed branch | not decided |
unknown.--deployment cloud stays unknown.Mitigations are separate from version status. Vendor workarounds are to disable the IBE service, to block internet access to the FortiMail webmail interface (or restrict it to a trusted private network), or, with a web application firewall in front, to block POST requests to /ibe containing ../. Reporting them (--ibe-service disabled, --webmail-exposure restricted) lists them in the result but never changes the version status. The PSIRT page also publishes indicators of compromise; consult it rather than relying on this tool.
[!WARNING] Unresolved source conflict: FortiMail 7.0. The CVE record's structured affected data (cveawg.mitre.org) lists 7.0.0-7.0.9 as affected, but the CVE description text, the PSIRT table, and the CERT-In bulletin list only 8.0, 7.6, 7.4, and 7.2. The structured data's 7.6 and 7.4 upper bounds (7.6.5 and 7.4.6) also differ from the PSIRT table. The CVE record's CNA solution text further says "Upgrade to upcoming FortiMail version 8.0.1 / 7.6.6 / 7.4.8 / 7.2.10 or above", lists FortiRecorder fixes (7.6.1, 7.2.12, 7.0.7), and puts FortiMail Cloud at "version 25.1 (not released)"; this contradicts the PSIRT table (Solution update 2026-10-05). The PSIRT table is used, 7.2.10 is not treated as a fix, and CERT-In's "management interface" wording differs from the PSIRT's "webmail interface" (the PSIRT wording is used). Every 7.0 release stays
unknownuntil explicit vendor evidence resolves this.
Input modes can be combined; each entry becomes its own result row (up to 10,000 per run, with input files limited to 4 MiB). Inputs must be regular files. The complete input, output, and field specification is in docs/REFERENCE.md.
| Option | Description |
|---|---|
--fortimail-version VERSION | Assess a reported plain MAJOR.MINOR.PATCH version (optional leading v); repeatable. |
--inventory FILE | JSON object or array of objects with schema_version (1) and version; repeatable. See inventory.example.json. |
--list FILE | UTF-8 CSV with a header row; version is required. Optional columns: label, build_source, deployment, ibe_service, webmail_exposure. Repeatable. |
Example CSV list:
label,version,ibe_service
mail-a.example.test,7.6.6,disabled
--build-source, --deployment, --ibe-service, and --webmail-exposure apply to every --fortimail-version on the command line; inventory and list entries carry them per entry.