Check these three things.
-
System owner: confirm whether each FortiMail 8.0 unit outside Fortinet-run FortiMail Cloud has 8.0.2 or above.
Fixes for other version groups
- Find every FortiMail unit your team or a hosting provider runs.
- FortiMail versions belong to groups named by their first two numbers. For example, 7.6.5 is in the 7.6 group.
- Fortinet's fixes for CVE-2026-126147:
- 8.0.0 through 8.0.1: upgrade to 8.0.2 or above.
- 7.6.0 through 7.6.6: upgrade to 7.6.7 or above.
- 7.4.0 through 7.4.8: upgrade to 7.4.9 or above.
- 7.2, all versions: "Migrate to a fixed release." Fortinet names no fixed 7.2 release.
- Source difference for 7.2:
- Fortinet's advisory and the CVE description say all 7.2 versions are affected.
- The CVE record's version list stops at 7.2.9.
- That list does not show that any later 7.2 release is fixed.
- FortiMail Cloud:
- Fortinet says it remediated FortiMail Cloud on October 5, 2026 by updating it to 7.6.7 or 8.0.2.
- Fortinet says FortiMail Cloud customers "need not perform any action."
- A FortiMail virtual machine your team or a provider runs in a cloud account is not that service.
- Companion CVE-2026-126148:
- It affects 8.0.0 through 8.0.1 and 7.6.0 through 7.6.6.
- The same 8.0.2 and 7.6.7 releases fix it.
- Fortinet says 7.4 and 7.2 are not affected.
- Record these fields:
- Unit.
- Installed version.
- Source of the version.
- Date checked.
-
Network owner: establish which networks can reach each unit's FortiMail API, which the sources do not tie to a specific interface.
API versus email sign-in
- The API is the interface other software uses to send requests to the unit.
- Fortinet names the API as the affected component.
- The attacker does not need to sign in.
- The sources do not establish:
- The exact API address or path.
- Which interface or service exposes the API.
- Whether a webmail or administrative sign-in page also exposes it.
- A reachable email sign-in page proves neither exposure nor safety. Include its interface in this check.
- Fortinet's guide says one HTTPS setting allows "secure HTTPS connections to the administrative GUI, webmail, and personal quarantine through this network interface." It does not say whether that setting covers the API.
- Public mail delivery is a separate path. Outside mail servers deliver through the unit when the domain's public MX record points to it. That path does not show API access.
- If your records do not show which interface serves the API, ask Fortinet or the provider.
- Records to use:
- Interfaces with administrative access enabled.
- Interfaces with webmail access enabled.
- Firewall rules for those interfaces.
- Source of each record.
- Date of each record.
- Companion HA flaw:
- CVE-2026-126148 uses crafted HA join-request packets, not the API.
- HA (high availability) means paired units that can take over for each other.
- It applies only to 8.0 and 7.6 units.
- Whether a unit without HA configured is affected is not established.
- For 8.0 and 7.6 units, record which networks can reach HA connections.
-
Security owner: review existing records for unexpected access, changes or mail interruption on units that ran an affected version.
Records that can show harm
- Include units already updated.
- Records to review:
- Administrator sign-in records.
- Configuration change records.
- Mail-flow records.
- Service alerts.
- Look for activity that does not match approved work.
- Act on unauthorized access or changes even if this CVE is not shown to be the cause.
- Limits:
- The retrieved sources give no specific signs of attack.
- An update does not rule out earlier harm.
- A clean log is not proof of no harm.
- Missing logs leave the question open.
- A mail interruption alone does not prove this flaw.
- A mail interruption alone does not prove a break-in.
If a unit runs an affected version, move it to a fixed release now. An update does not rule out earlier harm, so review its records too.