FortiMail CVE-2026-104286: 7.2.10 Fix Coming, None for EOL 7.0
Update, November 10, 2026: FortiMail 7.2 reached end of support today, and the fix Fortinet listed for it has not been released. The advisory still gives the solution for 7.2 as an upgrade to the upcoming 7.2.10, and Fortinet's documentation lists no 7.2 release after 7.2.9. FortiMail 7.0 and this flaw are now in our Exploited & Unpatchable feed, because Fortinet gives that branch no fix. FortiMail 7.2 is not in the feed: Fortinet has said a fix is coming, and the feed lists only what a vendor will not fix.
Update, October 28, 2026: Fortinet has changed its advisory. FortiMail 7.2 now has a fix listed as upcoming, 7.2.10, and FortiMail 7.0, which is past end of support, is now listed as affected with no fix. Until this change the advisory gave 7.2 only an upgrade path to 7.4 and did not mention 7.0. The change carries no new timeline entry; the advisory's updated date is still October 7, 2026.
FortiMail has an exploited flaw, fixed builds for three branches, a fix on the way for a fourth, and an end-of-life branch that gets none. Fortinet's advisory FG-IR-26-175, published October 1, 2026, describes CVE-2026-104286: a path traversal combined with a NULL-byte handling flaw that, in Fortinet's words, "may allow an unauthenticated attacker to write arbitrary files on the underlying system via crafted HTTP or HTTPS requests". Fortinet rates it critical, CVSS 9.8, and states that it "has been reported to be exploited in the wild". The advisory lists every branch from 7.2 to 8.0 as affected. For 7.4, 7.6 and 8.0 it names the release that carries the fix: first listed as upcoming, then named as fixed builds in the advisory's solution update of October 5, 2026. For 7.2 it now lists an upcoming 7.2.10, and for 7.0 it lists all versions as affected with the solution "Migrate to a fixed release".
What Fortinet says, branch by branch
The affected ranges and solutions are Fortinet's, from the advisory. The two lifecycle columns are Fortinet's end of engineering support and end of support dates as we serve them on the FortiMail page.
| Branch | Affected | Fortinet's solution | End of engineering support | End of support |
|---|---|---|---|---|
| 8.0 | 8.0.0 through 8.0.1 | Upgrade to 8.0.2 or above | May 6, 2029 | November 6, 2030 |
| 7.6 | 7.6.0 through 7.6.6 | Upgrade to 7.6.7 or above | August 1, 2027 | February 1, 2029 |
| 7.4 | 7.4.0 through 7.4.8 | Upgrade to 7.4.9 or above | July 4, 2026 | January 4, 2028 |
| 7.2 | 7.2.0 through 7.2.9 | Upgrade to upcoming 7.2.10 or above | May 10, 2025 | November 10, 2026 |
The advisory now also lists FortiMail 7.0, all versions, as affected, with the solution "Migrate to a fixed release": no 7.0 build. FortiMail 7.0 reached end of support on November 17, 2025. The advisory says nothing about branches older than 7.0; an appliance on one should be treated as exposed.
7.2: from an upgrade path to a coming fix
FortiMail 7.2 was still a supported branch when the flaw was disclosed. Its end of support came on November 10, 2026. But Fortinet's lifecycle has two dates per branch, and 7.2 had already passed the first one, end of engineering support, on May 10, 2025. When the advisory first appeared it showed what being past that date can mean in practice: the solution for 7.2 was to move to 7.4. As read on October 28, 2026, Fortinet now lists an upcoming 7.2.10 instead.
Note what that does to the 7.4 branch as well. FortiMail 7.4 passed its own end of engineering support on July 4, 2026, and it is still getting a build for this flaw, 7.4.9. So being past engineering support does not by itself decide the outcome. The branch that does go without a fix is 7.0, which is past end of support altogether.
The workaround
Fortinet gives three options, in this order:
- Disable IBE. In the GUI: Encryption, IBE, IBE Service off. In the CLI:
config system encryption ibe,set status disable,end. IBE is FortiMail's identity-based encryption; switching it off affects encrypted mail delivered through IBE, so check who relies on it first. - Take the webmail interface off the internet, or limit access to a trusted private network.
- If a web application firewall sits in front of FortiMail, block POST requests to
/ibethat contain a path traversal sequence (../).
The advisory also publishes indicators of compromise: two source IP addresses, system event log lines showing a cron job created under root and an unexpected remote archive account, and IBE decryption errors in the encryption log. Read the advisory for the exact strings and check the logs before treating a mitigated appliance as clean.
What to do, by branch
8.0, 7.6 and 7.4: install the fixed build the advisory names (8.0.2, 7.6.7 or 7.4.9); apply the workaround until the upgrade window arrives. Check the logs against Fortinet's indicators either way.
7.2: apply the workaround now and install 7.2.10 if Fortinet releases it; the branch reached end of support on November 10, 2026, so move off it rather than wait. Branch 7.4 is itself past engineering support and ends on January 4, 2028. Moving to 7.6 in the same change window lands on a branch with engineering support until August 1, 2027.
7.0: listed as affected, no fix; Fortinet's solution is to migrate to a fixed release. Apply the same mitigations, assume exposure, and move to a supported branch. Older than 7.0: not addressed by the advisory; treat as exposed and move.
FortiMail Cloud: nothing to do. Fortinet's advisory, in a clarification added on October 7, says it remediated FortiMail Cloud on October 5, 2026 by updating all firmware to 7.6.7 GA or 8.0.2 GA, so Cloud customers need not perform any action.
Frequently Asked Questions
Is there a patch for FortiMail CVE-2026-104286?
Yes, for three of the five affected branches, with a fourth coming. Fortinet's advisory FG-IR-26-175 first listed the fixes as upcoming; its solution update of October 5, 2026 names them as fixed builds: 8.0.2 for the 8.0 branch, 7.6.7 for 7.6 and 7.4.9 for 7.4. For 7.2 the advisory now lists an upcoming 7.2.10; for 7.0, which is past end of support, it gives no fix, only a migration to a fixed release. Until an appliance is upgraded, Fortinet's workaround is to disable the IBE service, or to block internet access to the FortiMail webmail interface.
Will FortiMail 7.2 get a fix for CVE-2026-104286?
Fortinet says so, but it has not shipped. As read on November 10, 2026, the advisory lists 7.2.0 through 7.2.9 as affected and gives the solution for that branch as an upgrade to the upcoming 7.2.10 or above; earlier versions of the advisory told 7.2 to move to branch 7.4. FortiMail 7.2 reached end of support that same day with 7.2.10 still unreleased. Until it is released, the workaround is the only protection.
What is CISA's deadline for CVE-2026-104286?
CISA added CVE-2026-104286 to its Known Exploited Vulnerabilities catalog on October 1, 2026 with a due date of October 4, 2026 for federal agencies. The required action is to apply the vendor's mitigations under BOD 26-04, or to discontinue use of the product if mitigations are unavailable, and the entry points to CISA's forensics triage requirements.
Is FortiMail 7.2 still supported?
No. FortiMail 7.2 is past both of its lifecycle dates: Fortinet's lifecycle gives end of engineering support as May 10, 2025 and end of support as November 10, 2026. When the advisory first appeared, 7.2 was offered an upgrade path to 7.4; Fortinet has since listed an upcoming 7.2.10 for it.
What is the workaround for CVE-2026-104286?
Fortinet gives three options: disable IBE feature support (Encryption, IBE, IBE Service off, or the CLI command config system encryption ibe, set status disable); or remove internet access to the FortiMail webmail interface, limiting it to a trusted private network; or, where a web application firewall sits in front of FortiMail, block POST requests to /ibe that contain a path traversal sequence.
Related
- FortiMail — every branch with Fortinet's two lifecycle dates
- Cisco Secure Email Gateway CVE-2026-76461 — September's email-gateway listing, and the same question about a branch inside its support window
- FortiOS 7.2 end of support — how Fortinet's two-date lifecycle works on its firewall line
- EOS Edge Device List — every edge platform we track with a CISA KEV history
- Exploited & Unpatchable — the feed of KEV entries on products past their fix window
- How we verify our dates — the rules every number on this site is held to