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.
Do Now
- System owner: update each affected FortiMail 8.0 unit outside Fortinet-run FortiMail Cloud to 8.0.2 or above.
Other groups and proof
- Other version groups:
- 7.6.0 through 7.6.6: update to 7.6.7 or above.
- 7.4.0 through 7.4.8: update to 7.4.9 or above.
- 7.2: Fortinet names no fixed 7.2 release. Migrate as Fortinet directs.
- 8.0.2 and 7.6.7 also fix companion CVE-2026-126148.
- Proof the update is done:
- Unit.
- Installed version after the work.
- Source of the record.
- Date checked.
- Other version groups:
- System owner: migrate each FortiMail 7.2 unit to a fixed release that Fortinet names.
No fixed 7.2 release is named
- Fortinet lists all 7.2 versions as affected.
- Fortinet's solution is "Migrate to a fixed release."
- Ask Fortinet which release each unit should use.
- Proof the migration is done:
- Release Fortinet named.
- Source and date of that answer.
- Installed version after the work.
- Date checked.
- Network owner: limit administrative access to trusted private networks, in addition to the update.
What this does not replace
- Fortinet's guide says: "Enable administrative access only on network interfaces connected to trusted private networks or directly to your management computer."
- The advisories give the upgrade, or migration for 7.2, as the solution.
- The advisories do not say this limit blocks the API flaw.
- Evidence fields:
- Unit.
- Interfaces with administrative access enabled.
- Networks that can reach them.
- Source of the record.
- Date checked.
- Security owner: start incident response if records show access or changes nobody approved.
When to escalate
- Preserve existing logs before changes, where this does not delay the update.
- Act even if this CVE is not shown to be the cause.
- Evidence fields:
- Records reviewed.
- Source of the records.
- Period covered.
- Date reviewed.
- Operations owner: handle any mail interruption or unexpected delivery change as a service incident now.
What a mail problem shows
- Handle it even if this flaw is not shown to be the cause.
- Send signs of unauthorized access to the Security owner.
- A mail problem alone does not prove this flaw.
- A mail problem alone does not prove a break-in.
- Evidence fields:
- Records reviewed.
- Source of the records.
- Date reviewed.
Do Next
- Security owner: recheck Fortinet's advisories and the KEV catalog for a change in exploitation status.
Why the current check is limited
- Fortinet's advisories, published November 10, 2026, list Known Exploited: No for both flaws.
- That is not proof that no attacks occurred.
- KEV catalog version 2026.11.13 was released November 13, 2026.
- The CVE records were published November 11, 2026.
- A November 14, 2026 check of that catalog found no entry for either CVE.
- CISA assessed both CVE records using SSVC 2.0.3, dated November 13, 2026.
- Exploitation: none. Automatable: yes. Technical Impact: total.
- SSVC “none” does not prove that no attacks occurred. SSVC assessments and KEV membership are separate.
- If a later source reports exploitation, review the affected units' records again.
- Evidence fields:
- Source checked.
- Status found.
- Date checked.
Check your own records.
- Use your approved AI tool.
- Require evidence. Flag unknowns.
Read the prompt
The reported finding
CVE-2026-126147: path traversal in the FortiMail API
Original advisory →- Required conditions
- Affected FortiMail versions:
- 8.0.0 through 8.0.1.
- 7.6.0 through 7.6.6.
- 7.4.0 through 7.4.8.
- All 7.2 versions, according to Fortinet.
- Crafted requests that reach the API.
- No sign-in needed.
- The sources do not name the API endpoint or the interface that exposes it.
- Affected FortiMail versions:
- Reported outcome
- Path traversal (CWE-22) means a request reaches files or folders outside the area it should be limited to.
- Fortinet says it "may allow an unauthenticated attacker to execute unauthorized code or commands via crafted requests."
- Fortinet rates it Critical, CVSS 3.1 score 9.8.
- Fortinet says it was discovered internally.
- Actual harm is limited by the unit's role and permissions.
Companion CVE-2026-126148: command injection in HA join handling
Original advisory →- Required conditions
- Affected FortiMail versions:
- 8.0.0 through 8.0.1.
- 7.6.0 through 7.6.6.
- Crafted HA join-request packets that reach the unit.
- No sign-in needed.
- Whether a unit without HA configured is affected is not established.
- Affected FortiMail versions:
- Reported outcome
- Command injection means input from a request is run as a system command.
- Fortinet classes it as CWE-77 in the CLI component. The CVE record calls it OS command injection.
- Fortinet says it may allow an unauthenticated attacker to execute unauthorized code or commands.
- Fortinet rates it Critical, CVSS 3.1 score 9.8.
- The CVE record's CVSS vector rates exploit code maturity as Proof-of-Concept (E:P). For CVE-2026-126147 it is Unproven (E:U). These ratings are not reports of attacks.
Fix guidance
- Fortinet FG-IR-26-199: fixes for the 8.0, 7.6 and 7.4 groups, and migration for 7.2
- Fortinet FG-IR-26-200: companion fixes in 8.0.2 and 7.6.7
- Boundaries:
- Fortinet says it remediated Fortinet-run FortiMail Cloud on October 5, 2026.
- That does not cover FortiMail units or virtual machines your team or a provider runs.
- The CVE record's 7.2 range stops at 7.2.9, while Fortinet says all 7.2 versions.
- Current status and history:
- An update fixes the current state.
- It does not rule out earlier harm.
- Units that ran an affected version stay in the record review.
- Exploitation evidence:
- Fortinet lists Known Exploited: No, as of November 10, 2026.
- KEV catalog version 2026.11.13 had no entry for either CVE when checked November 14, 2026.
- That catalog was released November 13, 2026, after the CVE records were published.
- No entry is not proof of no exploitation.
- CISA assessed both CVE records using SSVC 2.0.3, dated November 13, 2026.
- Exploitation: none. Automatable: yes. Technical Impact: total.
- SSVC “none” does not prove that no attacks occurred. SSVC assessments and KEV membership are separate.
What IntegrityLab.ai can check
- Authorized web discovery records four facts about a reachable web service:
- Response status.
- Page title.
- Content length.
- Server identification.
- Limits:
- No check for CVE-2026-126147 or CVE-2026-126148 was found in the inspected code.
- It does not establish FortiMail version or fix status.
- It does not establish API or HA exposure.
- It does not establish compromise.
- A front server can hide the system behind it. Missing identification does not rule FortiMail out.
- No web check establishes HA reachability.
- An observed sign-in page can point an owner to a service to investigate. It does not show whether that service exposes the FortiMail API.
Sources and vendor guidance
- Original advisory: Fortinet FG-IR-26-199 (CVE-2026-126147)
- Companion advisory: Fortinet FG-IR-26-200 (CVE-2026-126148)
- CVE-2026-126147 record (raw JSON)
- CVE-2026-126148 record (raw JSON)
- Vendor guidance: FortiMail network settings
- FortiMail deployment guide: public MX record
- CISA KEV catalog data (raw JSON, version 2026.11.13 checked November 14, 2026)