# Email gateway playbook: the first 72 hours after a critical flaw

Playbook, sources read 19 Nov 2026

**The short answer.** A mail gateway reads every message and faces the internet, so a flaw in it exposes mail content as well as the box. Using Fortinet's FortiMail CVE-2026-104286, this playbook gives the hour-by-hour order: check IBE, close webmail, preserve logs, hunt the published lines and addresses, then upgrade.

A mail gateway is the one server that sees every inbound and outbound message in clear text, and its web interface (webmail, the secure-message portal, the admin console) is usually reachable from the internet so that outside recipients can open encrypted mail. Flaws in these interfaces are exploited by sending crafted web requests to that interface. CVE-2026-104286 is listed under path traversal (CWE-22) and improper neutralization of a NULL byte (CWE-158): an unauthenticated visitor sends crafted HTTP or HTTPS requests and writes arbitrary files on the appliance, and Fortinet lists the impact as execution of unauthorized code or commands.

What the attacker gains is mail, not only a foothold. The indicators Fortinet published from compromised appliances show a root cron job, an admin session that logged out for no reason, and a new mail archive account whose destination is a remote server. An archive account like that copies mail passing through the appliance to a machine the attacker owns. What makes patching hard is that an upgrade means a reboot and a gap in mail flow, the workaround that works (turning off the IBE service) breaks encrypted mail delivery for some users, and older trains may have no fixed build at all.

## The steps, hour by hour

| Window | Owner | Step, and why it comes here | Record to keep |
| --- | --- | --- | --- |
| 0 to 1 hour | Security lead | List every FortiMail appliance and virtual machine, including lab and disaster-recovery copies, and read its build. In the CLI run get system status and read the Version line, or open Dashboard > Status > System Information. Affected builds: 8.0.0 to 8.0.1, 7.6.0 to 7.6.6, 7.4.0 to 7.4.8, 7.2.0 to 7.2.9, and every 7.0 build. First fixed builds: 8.0.2, 7.6.7, 7.4.9; 7.2.10 was listed only as upcoming in the advisory revision of 7 Oct 2026; 7.0 has no fixed build and Fortinet says to migrate. FortiMail Cloud needs no action: Fortinet updated it on 5 Oct 2026 to 7.6.7 GA or 8.0.2 GA, and get system status on a Cloud instance should report one of those.<br>The version decides which of the later steps apply, and a 7.2 or 7.0 appliance can never be fixed by upgrading today. | One row per appliance: name, train, exact build, HA role, internet-facing yes or no. |
| 0 to 1 hour | Platform engineering | Read the two settings that make the flaw reachable. IBE: GUI Encryption > IBE > IBE Service, or CLI show full-configuration system encryption ibe and look for set status enable. Web exposure: CLI show system interface and read set allowaccess on each interface for http and https, then from a host outside your network run nc -vz <appliance-ip> 443 and nc -vz <appliance-ip> 80. Also read the firewall and NAT rules that publish the appliance.<br>Fortinet ties its workaround and its log lines to IBE, but does not state IBE as a formal prerequisite, so an appliance with IBE off and a public web interface is still handled as exposed. | For each appliance: IBE status, interfaces that allow http or https, result of the outside port test. |
| 1 to 2 hours | Security lead | Before changing anything, take a configuration backup and export Log > Event > System and Log > Encryption for the longest period the appliance retains, and copy them to storage the appliance cannot write to. Snapshot a virtual appliance. CISA's KEV entry marks forensic triage as required, and the actor's first step after exploitation is to alter the box.<br>Logs on the appliance are the evidence, and the workaround, the upgrade and a reboot all change them. | File names, hashes and the time the export finished; who held the copy. |
| 2 to 4 hours | Platform engineering | Apply one workaround on each exposed appliance, in this order of preference. (1) Turn the IBE service off: GUI Encryption > IBE > IBE Service off, or CLI config system encryption ibe, set status disable, end. (2) If IBE must stay on, remove internet access to webmail and allow it only from trusted private networks, by firewall rule or by removing http and https from allowaccess on the public interface. (3) If a web application firewall sits in front, block POST requests to /ibe that contain ../ , the pattern Fortinet names. Re-run the read from step 2 afterwards.<br>Fortinet published the workaround at disclosure because exploitation was already reported, and it closes the path in minutes while a build takes a maintenance window. | Which option, time applied, who approved the loss of IBE delivery, and the result of the second port and setting read. |
| 2 to 4 hours | Security lead | Search the exported logs for the lines Fortinet published. System event log: type=event subtype=system pri=debug user=system ui=cron msg="(root) CMD (/bin/sh -c 'O=/migadmin ..."; type=kevent subtype=admin pri=information user=admin ui=(null) action=logout status=success reason=unknown msg="User admin logged out from (null)."; and type=kevent subtype=config ... msg="Added 'archive234' to 'archive account'" with rotation-size[50], rotation-time[1], rotation-hour[14], destination[remote], remote-ip[79[.]141[.]169[.]187], remote-username[archive234], remote-directory[/uploads] (user: admin, from: cli). Encryption log: FortiMail::IBE::DecrypterMediaIn ... Caught BufferException(2), BufferImpl.cpp:973, 'Invalid Base64 Encoding at pos 0. Character=0x2a', followed by Internal user *@domain.tld failed to log in. Then open the archive account settings and look for any account you did not create, not only one named archive234.<br>A hit changes the job from patching to incident response before you upgrade and reboot. | Each matching line with its timestamp, and the full list of archive accounts with creator and date. |
| 2 to 4 hours | Network security | Search firewall, proxy and NetFlow records for the appliance talking to 79[.]141[.]169[.]187 or 45[.]129[.]0[.]192, in both directions, for as far back as you keep records. Check specifically for outbound sessions from the appliance's own address, because the archive account sends mail to a remote server.<br>Fortinet gives exactly two attacker addresses, so a hit is strong evidence, and outbound traffic from the gateway is the sign mail was copied out. | Query text, time range searched, hits with first and last seen. |
| 4 to 24 hours | Platform engineering | Upgrade to the first fixed build for the train: 8.0.2, 7.6.7 or 7.4.9, or later. Back up the configuration first. On an HA pair, upgrade the secondary, fail over, check mail flow, then upgrade the former primary. Warn the mail team that each node reboots. For 7.2, stay on the workaround until Fortinet lists 7.2.10 as released. For 7.0, start the migration to a fixed train now. After the reboot run get system status and confirm the new Version line.<br>The workaround stays in place until the version read proves the fix, because the upgrade is the riskiest change for mail flow. | Build before and after, time of each node, mail queue length before and after, and any bounced mail. |
| 4 to 24 hours | Security lead | If any indicator matched, treat the appliance as compromised with root access: do not clean it in place. Rebuild from a clean fixed image and restore a configuration backup dated before the first indicator, then change every credential the appliance holds (admin accounts, directory bind accounts, TLS private keys and API tokens). Work out what was copied: the archive account's creation time marks the start, and its rotation settings show how often it sent mail out. Ask legal whether those messages include regulated data.<br>Fortinet's own indicators include a root cron entry, so file-level cleanup cannot be trusted. | Time of the first indicator, time the archive account was removed, mailboxes and domains in the copy window. |
| 24 to 72 hours | Application owner | Test inbound and outbound delivery, spam filtering, DKIM signing and TLS policy, then re-enable IBE only on a build the version read confirms as fixed. Tell the users of IBE secure mail when delivery returns. Re-run the whole check list from step 1 on every appliance as a closing read, and keep the outside port test on the schedule.<br>A feature turned off as a workaround is easy to forget, and IBE users have no other path to open secure mail. | Time IBE came back, test messages sent, and the closing version table. |
| 24 to 72 hours | Executive | Decide the open items with a date each: the 7.2 appliances waiting for 7.2.10, the 7.0 appliances that must migrate, and whether the web interface needs to face the internet at all. CISA gave 4 Oct 2026 as the due date for this entry, three days after listing, so the same 72 hours were the public deadline.<br>These are budget and mail-service decisions, not security-team decisions. | Owner and date for each open appliance. |

Print this table as the checklist: write the time each step was done in the record column.

## When no fix exists yet

With FortiMail the fix gap is real: 7.2 had no released fix in the last advisory revision read, and 7.0 has none. The mitigations are the three in the workaround. Turning IBE off costs the secure portal: recipients can no longer open or reply to IBE messages, and users whose policies depend on IBE lose that delivery path. Closing webmail to the internet costs the same users, plus any outside user of webmail. The WAF rule costs writing and testing the pattern, and it only covers the traversal string that Fortinet named, so treat it as a second layer and not a reason to leave IBE on.

Take the appliance offline when logs show an indicator, or when none of the three mitigations can be applied (for example the secure portal is needed and no WAF exists). CISA's action for the entry says to follow vendor instructions, apply BOD 26-04 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Offline is less costly than it sounds: sending servers retry for days (RFC 5321 says to keep trying for at least 4 to 5 days), so a gateway outage of a day delays mail but need not lose it, provided a secondary route does not bypass the filtering you are trying to protect.

## CVE-2026-104286 worked through, day by day

Fortinet's own Product Security team found the FortiMail flaw, and the advisory FG-IR-26-175 of 1 Oct 2026 already said it was reported as exploited in the wild. The sources give dates but no hours, so the table runs in days from disclosure. The first row is Day 0.

| When | What happened | Source |
| --- | --- | --- |
| 1 Oct 2026 (Day 0) | Fortinet publishes FG-IR-26-175: CVSS 3.1 base 9.8 (temporal 8.8), Known Exploited: Yes, with the IBE workaround, two attacker addresses and the log lines. | [source](https://fortiguard.fortinet.com/psirt/FG-IR-26-175) |
| 1 Oct 2026 (Day 0) | CISA adds the CVE to KEV the same day, forensic triage required: Yes, due date 4 Oct 2026, ransomware use Unknown. | [source](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-104286) |
| 2 Oct 2026 (Day 1) | CISA's SSVC entry on the NVD record is stamped: exploitation active, automatable yes, technical impact total. | [source](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-104286) |
| 4 Oct 2026 (Day 3) | KEV due date. | [source](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-104286) |
| 5 Oct 2026 (Day 4) | Fortinet revises the advisory (solution update) and says it updated FortiMail Cloud to 7.6.7 GA or 8.0.2 GA that day. | [source](https://fortiguard.fortinet.com/psirt/FG-IR-26-175) |
| 7 Oct 2026 (Day 6) | Second revision (FortiMail Cloud fix clarification). The table still lists 7.2 as 'Upgrade to upcoming 7.2.10 or above' and 7.0 as 'Migrate to a fixed release'. | [source](https://fortiguard.fortinet.com/psirt/cvrf/FG-IR-26-175) |

An owner who started the clock at 1 Oct had the workaround, the IP list and the log lines in the first advisory, so steps 1 to 6 (version read, evidence copy, workaround, log hunt, address search) fit inside four hours of Day 0, and no fixed build was needed to close the hole. Upgrading 8.0, 7.6 and 7.4 appliances inside 24 hours would be done by 2 Oct, two days before the KEV due date of 4 Oct. The 72 hours also decided the 7.2 and 7.0 appliances: on 7 Oct, Day 6, the vendor table still had no released fix for them, so their only protection for at least those 6 days was the workaround, which is why the playbook puts the no-fix decisions in the 24 to 72 hour window and not later. No source gives a first exploitation date or a victim count, so the log hunt over the longest period the appliance retains is the only way to know whether a given appliance was hit before Day 0.

## Related pages

- [The remote support tool playbook for the first 72 hours](/playbooks/remote-support-tool/)
- [SaaS vendor playbook: the first 72 hours when the flaw is in a service you cannot patch](/playbooks/saas-vendor/)
- [The artifact repository and CI system playbook for the first 72 hours](/playbooks/artifact-repository/)

## Sources

- Fortinet PSIRT advisory FG-IR-26-175: https://fortiguard.fortinet.com/psirt/FG-IR-26-175 (read 19 Nov 2026)
- Fortinet advisory FG-IR-26-175, CVRF revision history: https://fortiguard.fortinet.com/psirt/cvrf/FG-IR-26-175 (read 19 Nov 2026)
- CISA KEV entry for CVE-2026-104286: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-104286 (read 19 Nov 2026)
- NVD record for CVE-2026-104286: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-104286 (read 19 Nov 2026)
- FortiMail CLI reference, system encryption ibe: https://docs.fortinet.com/document/fortimail/7.6.0/cli-reference/6402/system-encryption-ibe (read 19 Nov 2026)
- RFC 5321, section 4.5.4.1, sending strategy: https://www.rfc-editor.org/rfc/rfc5321#section-4.5.4.1 (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://zerodayplaybook.com/playbooks/email-gateway/
