Fortinet FortiMail, CVE-2026-104286: on CISA's exploited list
The bottom line
If you run FortiMail yourself (not FortiMail Cloud), act today: CISA's date of 4 October 2026 has passed. First turn off the IBE service or cut internet access to webmail, then upgrade. FortiMail Cloud customers can stop reading.
At a glance
| Fact | Detail |
|---|---|
| Product | Fortinet FortiMail (CVE-2026-104286) |
| Severity | Critical: 9.8 (CVSS 3.1) |
| CISA | On its exploited list since 1 October 2026. Deadline for US federal agencies: 4 October 2026. |
| Chance of exploitation (EPSS) | 0.05, the estimated chance in the next 30 days, as at 6 November 2026 |
| Ransomware use | Not recorded by CISA. That is not the same as none. |
| Fixed in | FortiMail 8.0.2, 7.6.7 and 7.4.9 (or above). 7.2.10 is described as upcoming. 7.0 has no fixed release named: migrate. Vendor advisory, updated 7 October 2026. |
| Who looks first | Anyone running their own FortiMail appliance or virtual machine on 8.0, 7.6, 7.4, 7.2 or 7.0, especially if webmail or the IBE service can be reached from the internet. |
Does this apply to you?
| Question | If no | If yes |
|---|---|---|
| Do you run FortiMail yourself, as an appliance or virtual machine? | Nothing to do for this CVE. | Check whether it is FortiMail Cloud (next question). |
| Is your FortiMail the vendor-hosted FortiMail Cloud service? | Check the version (next question). | The vendor says it fixed Cloud on 5 October 2026. Nothing to do. |
| Is your version in a range listed as affected, with no fix applied yet? | You are on a fixed release. Confirm it in writing, then check the logs. | Reduce exposure now, then upgrade. |
| Is the IBE service on, or is webmail reachable from the internet? | The exposure is lower. Still upgrade, since the vendor's workarounds are not a fix. | Apply a workaround today, then upgrade. |
What it is
An attacker with no login can send crafted HTTP or HTTPS requests to FortiMail and write arbitrary files on the underlying system. The vendor's advisory says this has been exploited in the wild and rates it Critical, CVSS 9.8.
Why it matters
The advisory says the flaw lets an unauthenticated attacker write files on the underlying system, and it lists the impact as executing unauthorised code or commands. Our reading is that a mail gateway is a useful foothold: it sits at the network edge and handles all inbound mail. The vendor's own indicators include a changed cron entry and a new archive account that sends data to a remote address. A low EPSS figure should not delay action when exploitation is already reported.
What the vendor's advisory says
We read one page on fortiguard.fortinet.com. In short:
- The vendor's advisory says fixes are in 8.0.2, 7.6.7 and 7.4.9 or above. 7.2.10 is described as upcoming.
- FortiMail 7.0, all versions, has no fixed release named. The advisory says to migrate to a fixed release.
- Workaround 1, from the advisory: switch the IBE service off in the GUI or with the CLI setting for IBE status.
- Workaround 2: block internet access to the webmail interface, or limit it to trusted private networks.
- Workaround 3: if a web application firewall sits in front, block POST requests to the IBE path that contain '../'.
Exposure by situation
These priorities are our judgement from what the sources say about who can use the flaw and how. They are not vendor ratings.
| Your situation | Priority | Timeframe |
|---|---|---|
| Self-run FortiMail on an affected version, with IBE or webmail open to the internet | High | Today: workaround now, upgrade as soon as possible |
| Self-run FortiMail on an affected version, webmail limited to a trusted private network | Medium | This week, upgrade |
| FortiMail 7.0, any version, with no fixed release named | High | Plan the migration now; use the workarounds meanwhile |
| Self-run FortiMail already on 8.0.2, 7.6.7 or 7.4.9 or later | Low | Check the logs once, then no further action |
| FortiMail Cloud only | None | None for this CVE |
Things people will get wrong
- "The score is 9.8 on paper, so it will not matter for us." The vendor's advisory says it is exploited in the wild and needs no login. The temporal score of 8.8 is still high.
- "We switched IBE off, so we are safe." That is a workaround, not a fix. The advisory also says to upgrade, and the flaw may already have been used before you switched it off.
- "Upgrading to 7.2.9 fixes it." 7.2.0 through 7.2.9 are listed as affected. The advisory names 7.2.10 as upcoming, not released.
How we would triage it
This is our judgement.
The commands only read: they print a version or list what is installed. They come from general knowledge of this kind of product, not from the sources, so check them against the vendor's page before you run them. Words in capitals are for you to fill in.
Step 1: Find the versions you run
- List every FortiMail you manage and note whether it is self-run or FortiMail Cloud.
- Compare each version with the affected ranges in the advisory.
get system status
show system encryption ibeStep 2: Reduce exposure
- Turn the IBE service off, or limit webmail to trusted private networks, as the advisory says.
- If a web application firewall sits in front, block POST requests to the IBE path that contain '../'.
Step 3: Upgrade
- Move to 8.0.2, 7.6.7 or 7.4.9, or above, as the advisory says.
- On 7.2, wait for 7.2.10. On 7.0, migrate to a fixed release.
Step 4: Check for signs of use
- Look for the indicators in the vendor's advisory: cron entries, new archive accounts, IBE decryption errors.
- If you find any, treat the appliance as compromised and follow CISA's forensic guidance.
To close it, read the version from the product itself, not from an old inventory, and save the output with the date. If you cannot update today, write down who owns it, the new date, and what limits exposure until then.
Send this to your IT provider
Copy it, change the names and dates, and send it. It is a draft for you to check, not a template tested with any provider.
Hello, we need to confirm our exposure to CVE-2026-104286, a path traversal flaw in Fortinet FortiMail that the vendor says is being exploited. Please tell us whether we run FortiMail ourselves or use FortiMail Cloud, and which version each system runs. The fixed releases are 8.0.2, 7.6.7 and 7.4.9 or above. Please disable the IBE service or restrict webmail access now, then upgrade. Please also check for the indicators in the vendor's advisory. We would like written confirmation of the versions and the fix by the end of this week.
Signs it was used
An update closes the hole. It does not tell you whether someone used it first. CISA's required action points to its forensic triage requirements (BOD 26-04). Look for:
- Cron entries in the system event log that run a script from an unfamiliar path.
- An archive account you did not create, sending files to a remote address.
- IBE errors about invalid Base64 encoding, or internal users failing to log in.
The weakness behind it
The record classes this as CWE-22 (Improper Limitation of a Pathname to a Restricted Directory).
Likely ATT&CK mapping
MITRE ATT&CK is a public catalogue of the steps attackers take, from getting in to causing damage. No source has mapped this flaw to it yet, so the steps below are our prediction from what the record says the flaw allows. They are not MITRE's, the vendor's or CISA's, and an attacker may do other things.
| The step, in plain words | Stage of an attack | Why we think so |
|---|---|---|
| Exploit Public-Facing Application (T1190): Breaking in through a service that faces the internet, such as a web server, VPN or login page. | Initial Access: getting in | The flaw is reachable over unauthenticated HTTP/HTTPS against FortiMail, which is typically internet-exposed; path traversal enabling arbitrary file write on a public-facing application would likely serve as the initial intrusion point. |
| Command and Scripting Interpreter (T1059): Running commands or scripts on a machine, such as a shell or PowerShell. | Execution: running the attacker's code | Arbitrary file write on the underlying system would typically allow an attacker to place a shell script or cron entry; the published IoC showing /bin/sh invoked via cron supports this as the likely next step after exploitation. |
| Account Manipulation (T1098): Changing an existing account, for example adding permissions or keys, to keep access. | Persistence: staying in | The IoC shows an archive account added via CLI with a remote destination IP, suggesting account manipulation for persistent access or staged exfiltration is a likely follow-on once arbitrary write is achieved. |
How to use this: ask your IT provider which control or log would show each step, for example whether sign-in attempts from the internet are recorded. If nobody can answer, that is the gap to close first.
MITRE ATT&CK® is a registered trademark of The MITRE Corporation. Technique names are MITRE's.
The sources, in their words
CISA's catalogue entry:
Fortinet FortiMail contains a path traversal and an improper neutralization of NULL byte or NULL character vulnerability that may allow an unauthenticated attacker to write arbitrary files on the underlying system via crafted HTTP or HTTPS requests.
The CVE record, published by Fortinet on 1 October 2026:
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.
Versions of Fortinet FortiMail the record lists as affected:
- 8.0.0 through 8.0.1
- 7.6.0 through 7.6.6
- 7.4.0 through 7.4.8
- 7.2.0 through 7.2.9
- 7.0.0 through 7.0.9
What the record says to do about it, in the vendor's words:
Upgrade to FortiMail version 8.0.2 or above Upgrade to FortiMail version 7.6.7 or above Upgrade to FortiMail version 7.4.9 or above Upgrade to upcoming FortiMail version 7.2.10 or above
CISA's required action:
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).
Check your own project
If you build software, you can compare what a project declares with this CVE from a terminal. The tool reads requirements files, package.json, Maven, Gradle, Cargo, CMake and Dockerfile files, runs nothing, and only the CVE id leaves your machine. Naming the CVEs needs no key.
lattice-scan project . --cve CVE-2026-104286Each row says in-range, outside-range, undetermined or lead, with the file and line. That is evidence about what a manifest declares, not about what runs, and a person decides. The verdicts, the CSV columns and a pipeline recipe are in the guide.
Check the servers you run
The same id can be checked against a host. Run this on the machine itself, not on the laptop that deploys to it: it reads installed packages (dpkg, rpm or apk), snaps, the hardware, the running container images with their operating system and packages, and the kernel version, compares them on the spot, and only the CVE ids leave the machine; the inventory stays on it, in ~/.lattice-scan. Naming the CVEs needs no key. Do it on each server after a deployment, and again when a new entry lands.
lattice-scan --cve CVE-2026-104286A match is a candidate for a person to confirm, not a finding. A distribution can fix a CVE under an unchanged version number, so a match is a candidate; on Debian-family hosts the report also shows whether the package's own changelog names the CVE. It reads the names of the running images, not what is inside them; for what an image declares, use the project check on its Dockerfile.
Guide: namiq.io/lattice/guides/choose-your-channel. MCP server (io.namiq/lattice in the MCP registry): namiq.io/lattice. Package: pypi.org/project/lattice-scan, or namiq.io/apt.
- Which way into Lattice fits your job →The command line, the Claude skill or the MCP server: what each needs, what works without a key and how to read the result.
- Lattice, the MCP server →The public graph the command reads, for AI agents over MCP.
- Install and connect →The signed apt repository, the fingerprint, and the connection commands for each client.
What we do not know yet
- The sources do not say how many systems have been compromised or how the attacks started.
- No release date is given for FortiMail 7.2.10.
- The record does not name a fixed 7.0 release, only that you should migrate.
- The sources do not say whether the IBE workaround removes all exposure.
- We have not tested this against any environment. Versions and scores are as the sources state them and as at 6 November 2026; the vendor's advisory wins where it differs.
- The sections headed "The bottom line", "Does this apply to you?", "What it is", "Why it matters", "Exposure by situation", "Things people will get wrong", "Likely ATT&CK mapping", "How we would triage it" and "Send this to your IT provider" are our interpretation of the sources, not a statement by CISA or the vendor.