P.K. SHARMA

Cyber security intelligence, AI governance, practitioner analysis

FortiMail zero-day: Fortinet's version lists disagree while the fixes are still upcoming

CVE-2026-104286 is exploited and permits an unauthenticated file write. Fortinet's prose and structured CVE record give different affected ranges, so an inventory can miss a build before an operator even reaches the workaround.

By · LinkedIn · · 8 min read

The first failure can happen in the asset list

Fortinet says CVE-2026-104286 is being exploited against FortiMail. The flaw lets a remote attacker send crafted HTTP or HTTPS traffic and write an arbitrary file on the appliance without authentication. Fortinet rates it 9.8. CISA added it to its Known Exploited Vulnerabilities catalogue on 1 October. These are two distinct facts: the vendor reports exploitation, and a government catalogue has accepted that status. Neither tells us how many organisations were compromised.

The less obvious problem is in the paperwork used to decide which appliances need action. Fortinet's advisory and the prose description in the CVE record include 8.0.1, 7.6.6 and 7.4.7 through 7.4.8. The structured affected-product field in that same CVE record stops before those releases, but adds 7.0.0 through 7.0.9, which the prose omits. An automated vulnerability feed and a human reading the bulletin can therefore make opposite calls on the same build.

That disagreement does not establish which field is right. It means neither the narrower machine-readable range nor the prose alone is a sound basis for marking an appliance safe. Read the union as a triage set, confirm exact builds, and ask Fortinet for a reconciled answer where the records diverge.

Five release trains, two official answers

Affected ranges checked 2 October 2026. This table reports the discrepancy; it does not resolve it.

FortiMail trainFortinet advisory and CVE proseStructured CVE affected field
8.08.0.0–8.0.18.0.0
7.67.6.0–7.6.67.6.0–7.6.5
7.47.4.0–7.4.87.4.0–7.4.6
7.27.2.0–7.2.97.2.0–7.2.9
7.0Not named7.0.0–7.0.9

The structured field's defaultStatus is unaffected, so a consumer that trusts its ranges could classify 8.0.1, 7.6.6 or 7.4.8 as outside scope. A prose-only workflow could overlook 7.0 entirely. There is no public evidence here that all of those builds are equally exploitable, and an editorial correction would be irresponsible. The operational response is to flag the conflicting builds for vendor confirmation rather than silently choosing the shorter list.

Fortinet currently lists 8.0.2, 7.6.7 and 7.4.9 as upcoming. For 7.2 the advisory points to upgrading to the 7.4 branch or above. A fixed version named in an advisory is not necessarily a downloadable package today. Change managers should check the actual release repository and supported upgrade path before telling teams the vulnerability has been patched.

The request crosses from a web endpoint to a filesystem path

The advisory names CWE-22 path traversal and CWE-158 improper neutralisation of a NULL byte or character. Together they are described as allowing an unauthenticated arbitrary file write through crafted HTTP or HTTPS requests. Fortinet's workaround references the identity-based encryption (IBE) feature and specifically suggests a WAF rule for POST requests to /ibe containing ../. That is a useful defensive indicator, but Fortinet has not published a complete exploit request or the full path of every observed payload.

IBE is FortiMail's encrypted-mail delivery flow. Its presence matters because teams may think of FortiMail as a mail gateway and overlook the webmail and IBE surface exposed to recipients. The crossing is simple to state: input supplied across the web boundary can influence a path on the underlying appliance. The public evidence supports a file-write primitive. Whether any particular victim had a shell launched, mail stolen, or other systems reached requires incident evidence that the advisory does not provide.

Fortinet published artefacts, not a universal attack chain

Fortinet's IOC section gives concrete places to look. It names added paths such as /data/lib/liblog.so, /data/bin/webconsole, /data/bin/mailservice and /data/etc/ld.so.preload, and modified paths including /bin/smit, /data/etc/httpd.conf and /data/migadmin.tar.gz. It also lists two IP addresses, 79.141.169.187 and 45.129.0.192, alongside log examples. One configuration-log example describes an archive234 archive account pointing at 79.141.169.187. Those details make the bulletin more useful than a generic 'check for compromise' instruction.

They also need restraint. The advisory does not say every listed file occurs in every case, nor does it connect each file to an identical request, execution sequence or outcome. A missing IOC is not a clearance certificate. Conversely, a matching filename without hash, timestamp and context is not proof of this specific exploit. Preserve logs and filesystem state before making changes, then compare the current vendor list with local baselines and outbound traffic.

Investigation leads published by Fortinet; verify against the live advisory and local evidence.

Evidence familyExamplesWhat it can answer
Added files/data/lib/liblog.so; /data/bin/webconsole; /data/bin/mailservice; /data/etc/ld.so.preloadWhether unexplained files appeared on the appliance
Modified files/bin/smit; /data/etc/httpd.conf; /data/migadmin.tar.gzWhether system or service material changed
Network and logs79.141.169.187; 45.129.0.192; archive-account log entryWhether suspicious configuration or outbound activity correlates

The workaround is operational, not merely a patch reminder

The vendor workaround gives three ways to reduce exposure while fixed releases are pending. Disable IBE through Encryption → IBE → IBE Service off, or use the documented CLI sequence config system encryption ibe, set status disable, end. Alternatively, remove public access to the FortiMail webmail interface or allow only a trusted private network. If a WAF fronts the appliance, Fortinet suggests blocking POST requests to /ibe that contain ../. These are vendor-stated mitigations, not proof that a previously exposed appliance was never exploited.

Each option has a dependency. Disabling IBE may interrupt a recipient-facing encrypted-mail workflow; restricting webmail requires checking every route, hostname and reverse proxy; a WAF signature covers a described request pattern and should not be presented as a universal fix for arbitrary path handling. Record which option was chosen, when it became active, and what testing confirmed it on the actual deployment. Then keep the appliance in the investigation queue if it was exposed before that point.

Decisions for an affected or possibly affected appliance.

SituationImmediate actionWhat remains
IBE not neededDisable the IBE service as Fortinet directsInspect earlier exposure and indicators
IBE or webmail neededRestrict access to trusted private networks; assess Fortinet’s WAF ruleVerify recipient access and residual public routes
Fixed release becomes availableTest and install the supported buildInvestigate past file writes; upgrading does not undo them

CISA’s date is a federal instruction, not a UK deadline

CISA's KEV entry was added on 1 October and names 4 October 2026 as the due date for the US federal action described in the catalogue. It also flags forensic triage. That date is not a universal legal patch deadline for UK operators. It does, however, reinforce that the case is not a speculative scanner finding: exploitation is recorded while fixed versions are still described as upcoming.

For a UK organisation, the practical sequence is to inventory FortiMail deployments, identify exposed webmail or IBE access, apply an available mitigation, and preserve evidence from systems that could have been reached. If the public records disagree on a build, escalate that exact version to Fortinet rather than closing the ticket from a feed. Communications to leadership should distinguish 'mitigated exposure', 'upgraded', and 'assessed for prior compromise'. None of those phrases means the other two happened.

What cannot be concluded from the public record

The public evidence supports urgency, with clear limits.

EstablishedNot established
Fortinet reports exploitation and an unauthenticated arbitrary-write flawHow many organisations were hit
Specific version fields disagreeWhich conflicting range is the intended correction
Vendor IOC paths, logs and IPs are publishedA universal post-exploitation chain for all victims
Fixed releases are listed as upcomingThat every fixed package is already available

This is the central distinction in the incident response: a mitigation can stop a known route now, but only investigation can answer whether it was used before the change. Fortinet's file and log indicators give investigators a starting point, not a substitute for a baseline, preserved evidence and appliance-specific review.

The operator decision

Take this with you

Do this in order

  • Record every FortiMail build and every public route to webmail and IBE, including proxies and alternate hostnames.
  • Treat the union of the two official affected lists as a triage set; request vendor confirmation for conflicting builds.
  • Apply Fortinet’s documented mitigation that fits the deployment, and verify it from outside the trusted network.
  • Preserve appliance logs and filesystem evidence; compare the current vendor IOC list with local baselines.
  • Track release availability, then upgrade through the supported path and repeat compromise assessment separately.

The headline is a zero-day file write. The operational lesson is narrower and harder: a machine-readable field can understate the same vendor's prose, and a named future fix can be mistaken for a present one. An appliance is not safe because a dashboard says it is outside a range. It is safe only after the exact build, exposed route, mitigation and earlier evidence have each been checked.

Sources

  1. PrimaryFG-IR-26-175 advisoryFortinetaccessed 2026-10-02
  2. PrimaryCVE-2026-104286 recordCVE Programaccessed 2026-10-02
  3. PrimaryKnown Exploited Vulnerabilities catalogueCISAaccessed 2026-10-02
  4. PrimaryConfiguring IBE encryptionFortinetaccessed 2026-10-02

Share this briefing

Know someone who owns this problem? Send it to them.

Related briefings

The briefing, in your inbox

Practitioner analysis of cyber and AI security news. No vendor noise.

How often

Every new briefing in one email, at 7am, or at 7am, 12:30pm and 6pm. Nothing is sent when nothing is new. Unsubscribe any time.