Contact us
← Article questionsWhat should we do?

CVEHit Business Advisory by IntegrityLab.ai

What should we do?

FortiMail API flaw can let outsiders run commands — CVE-2026-126147: Business Triage

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.
  • 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.

← Back to article questions

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…