CVEHit Business Advisory by IntegrityLab.ai
What’s the evidence?
FortiMail API flaw can let outsiders run commands — CVE-2026-126147: Business Triage
The reported finding
- 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.
- 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.
- 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.
- 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
← Back to article questions