Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

FortiMail HA Command Injection (CVE-2026-126148)

CVE-2026-126148 is a critical command injection flaw in FortiMail HA join-request handling.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-126148
Vendor
Fortinet
Affected Product
FortiMail
Exploitation
No exploitation reported
Published
2026-11-10

Fortinet says crafted HA join-request packets may let an unauthenticated attacker execute unauthorized code or commands.Fortinet rates the issue 9.8 on CVSS 3.1. Its advisory identifies the CLI component and lists fixed releases for FortiMail 8.0 and 7.6.

What it allows

How Does CVE-2026-126148 Affect FortiMail HA?

Fortinet describes improper neutralization of special elements in a command. The affected path processes crafted HA join-request packets, and the vendor names the CLI as the component.

On that path, an unauthenticated attacker may execute unauthorized code or commands. The advisory does not describe the internal command construction, so defenders should treat this as the vendor's stated outcome rather than a documented payload sequence.

The HA join-request condition matters when assessing exposure. Brandefense recommends checking which FortiMail appliances can receive HA join requests and prioritizing those on affected releases.

How Is This Different From the Other FortiMail CVEs?

CVE-2026-126148 concerns command injection through HA join requests. NVD separately describes CVE-2026-126147 as path traversal and CVE-2026-126164 as SQL injection.

Those records describe different weaknesses and broader affected release branches than this HA issue. Do not apply their version ranges to CVE-2026-126148; use Fortinet advisory FG-IR-26-200 for this flaw.

What Does Fortinet Say About Exploitation?

Fortinet marks this advisory 'Known Exploited: No.' CISA KEV catalog version 2026.11.10 does not list CVE-2026-126148.

Those dated statements do not make the exposure harmless. The 9.8 score reflects a network attack requiring neither privileges nor user interaction, with high confidentiality, integrity, and availability impacts in the published vector.

Who is affected

Which FortiMail Versions Are Affected by CVE-2026-126148?

Fortinet lists FortiMail 8.0.0 through 8.0.1 and 7.6.0 through 7.6.6 as affected. The vendor directs operators to upgrade to 8.0.2 or later, or 7.6.7 or later, respectively.

FortiMail 7.4 and 7.2 are marked not affected in this advisory. Fortinet says it updated FortiMail Cloud firmware on October 5, 2026, so Cloud customers need no action for this issue.

Inventory appliance versions and confirm whether HA join requests can reach each affected installation. Use the vulnerability management guide to organize verification across the fleet.

What Should Defenders Do Next?

Upgrade affected 8.0 and 7.6 appliances to Fortinet's fixed releases. After upgrading, verify the installed build and review the HA configuration against intended access.

Brandefense recommends reviewing available management and HA logs for unexpected join activity. The vendor advisory does not publish a detection rule or indicator for this flaw, so this is an operational check, not a vendor detection claim.

Track the two distinct FortiMail issues separately during vulnerability prioritization. The patch management entry can help document release verification after the update.

Tip: Check the branch before updatingFortinet fixes this HA issue in FortiMail 8.0.2 and 7.6.7 or later. The advisory marks 7.4 and 7.2 not affected.

Timeline

  1. 2026-10-05

    Fortinet says it remediated the issue in FortiMail Cloud by updating firmware to 7.6.7 GA or 8.0.2 GA.

  2. 2026-11-10

    Fortinet initially published advisory FG-IR-26-200.

  3. 2026-11-11

    NVD published its CVE-2026-126148 record.

What to do

  1. Identify affected appliances

    Find FortiMail 8.0.0 through 8.0.1 and 7.6.0 through 7.6.6. Check which installations can receive HA join requests.

  2. Install the fixed release

    Upgrade the 8.0 branch to 8.0.2 or later and the 7.6 branch to 7.6.7 or later, as Fortinet directs.

  3. Verify the update

    Confirm the installed build after maintenance and review HA settings and available logs for unexpected join activity. The log review is Brandefense guidance.

  4. Keep sibling flaws separate

    Track CVE-2026-126147 path traversal and CVE-2026-126164 SQL injection as distinct issues. Their affected version ranges are not this advisory's range.

What Brandefense can do

Frequently Asked Questions

What is CVE-2026-126148?

It is a FortiMail command injection flaw in HA join-request handling. Fortinet says crafted packets may let an unauthenticated attacker execute unauthorized code or commands.

Which FortiMail releases need an update?

Fortinet lists 8.0.0 through 8.0.1 and 7.6.0 through 7.6.6. Upgrade to 8.0.2 or later, or 7.6.7 or later, respectively.

Are FortiMail 7.4 and 7.2 affected?

Fortinet marks both branches not affected by CVE-2026-126148. The other November FortiMail CVEs have different version ranges.

Do FortiMail Cloud customers need to patch this flaw?

Fortinet says it remediated FortiMail Cloud on October 5, 2026, with 7.6.7 GA or 8.0.2 GA firmware. It says Cloud customers need no action.

Is CVE-2026-126148 known to be exploited?

Fortinet marks the advisory 'Known Exploited: No.' The CISA KEV catalog dated November 10, 2026, does not list the CVE.

Sources

  1. FG-IR-26-200: FortiMail command injectionFortinet
  2. CVE-2026-126148 DetailNational Vulnerability Database
  3. CVE-2026-126147 DetailNational Vulnerability Database
  4. CVE-2026-126164 DetailNational Vulnerability Database
  5. Known Exploited Vulnerabilities CatalogCISA
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →