Fortinet says crafted requests may allow an unauthenticated attacker to execute unauthorized code or commands.Fortinet rates the flaw Critical at CVSS 3.1 score 9.4. Its FG-IR-26-216 advisory was initially published on November 10, 2026.
What it allows
How Can CVE-2026-126164 Affect FortiMail?
Fortinet classifies the root cause as improper neutralization of elements in an SQL command, or CWE-89. The advisory identifies the API component and says an unauthenticated attacker may use crafted requests.
Fortinet says the possible outcome is unauthorized code or command execution. The source does not describe a request sequence or detection signature, so the exact path from injection to execution remains unspecified.
That possible impact makes affected, self-managed FortiMail installations a patch priority. Brandefense recommends assessing API reachability and access controls in each deployment, without assuming the same exposure for every installation.
What Do Fortinet and CISA Say About Exploitation?
Fortinet marked the issue “Known Exploited: No” when it published FG-IR-26-216. CVE-2026-126164 was absent from CISA KEV catalog version 2026.11.10, released before the NVD record.
These are dated statements, rather than a prediction of later activity. Brandefense recommends reviewing relevant FortiMail logs for unexpected administrative or system activity while arranging the vendor upgrade.
This SQL injection issue differs from the earlier FortiMail file-write vulnerability. The Fortinet November advisory overview puts the separate flaws in context.
Who is affected
Which FortiMail Versions Are Affected by CVE-2026-126164?
Fortinet lists four affected release lines in FG-IR-26-216. The table below preserves the vendor’s affected ranges and corresponding solutions for this SQL injection flaw.
| FortiMail line | Affected releases | Fortinet solution |
|---|---|---|
| 8.0 | 8.0.0 through 8.0.1 | Upgrade to 8.0.2 or above |
| 7.6 | 7.6.0 through 7.6.6 | Upgrade to 7.6.7 or above |
| 7.4 | 7.4.0 through 7.4.8 | Upgrade to 7.4.9 or above |
| 7.2 | All versions | Migrate to a fixed release |
Fortinet says it remediated this issue in FortiMail Cloud on October 5, 2026. The advisory says FortiMail Cloud customers need take no action for this issue.
Fortinet lists no virtual patch. Teams operating their own installations should confirm installed versions and apply the solution for the matching release line.
The vulnerability management guide explains how to prioritize remediation. Recheck Fortinet’s advisory before maintenance for any changed release guidance.
Timeline
- 2026-10-05
Fortinet says it remediated this issue in FortiMail Cloud.
- 2026-11-10
Fortinet initially published FG-IR-26-216 and marked Known Exploited as No.
- 2026-11-11
NVD published its Fortinet-sourced CVE-2026-126164 record.
What to do
-
Inventory FortiMail installations
Record the installed release and distinguish self-managed FortiMail from FortiMail Cloud. Compare every self-managed deployment with Fortinet’s four affected release lines.
-
Apply the release-line solution
Upgrade affected 8.0 to 8.0.2 or above, 7.6 to 7.6.7 or above, and 7.4 to 7.4.9 or above. Migrate every 7.2 deployment to a fixed release.
-
Review access and logs
Brandefense recommends checking API access controls and relevant logs for unexpected administrative or system activity. An anomaly is an investigation lead, not proof of this specific CVE.
-
Verify remediation
Confirm the installed release after maintenance. Recheck FG-IR-26-216 for updates to fixes and Fortinet’s exploitation status.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-126164 in Brandefense Atlas
The Atlas record of CVE-2026-126164: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What is CVE-2026-126164?
It is a FortiMail SQL injection flaw (CWE-89). Fortinet says crafted requests may allow unauthenticated code or command execution.
Which FortiMail versions are affected?
Fortinet lists 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, 7.4.0 through 7.4.8, and every 7.2 release.
How should FortiMail 7.2 be remediated?
Fortinet lists all 7.2 releases as affected and directs users to migrate to a fixed release.
Do FortiMail Cloud customers need to act?
Fortinet says it remediated this issue in FortiMail Cloud on October 5, 2026, so cloud customers need take no action for it.
Is CVE-2026-126164 known to be exploited?
Fortinet marked Known Exploited as No at publication. The CVE was absent from CISA KEV catalog version 2026.11.10; both are dated source statements.
Sources
- FG-IR-26-216: Improper neutralization of special elements used in an SQL commandFortinet PSIRT
- CVE-2026-126164National Vulnerability Database
- Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency