Fortinet says crafted requests may allow an unauthenticated attacker to execute unauthorized code or commands.Fortinet rates the API component flaw Critical at CVSS 3.1 score 9.8. The vendor published advisory FG-IR-26-199 on November 10, 2026.
What it allows
How Does CVE-2026-126147 Affect FortiMail?
Fortinet identifies the root cause as improper restriction of a pathname to a permitted directory. That classification is path traversal, recorded as CWE-22.
The vendor says an unauthenticated attacker may send crafted requests and execute unauthorized code or commands. The advisory identifies the API component but gives no request details or detection signature.
That outcome warrants urgent remediation for affected installations, especially where the FortiMail API is reachable. Exposure should be assessed from each deployment's access controls; the advisory does not define a universal network exposure condition.
What Is the Reported Exploitation Status?
Fortinet marked FG-IR-26-199 "Known Exploited: No" when it published the advisory. CVE-2026-126147 was absent from CISA KEV catalog version 2026.11.10, released before the NVD record.
Those are dated source statements, not a guarantee about subsequent activity. Brandefense recommends reviewing FortiMail logs for unexpected administrative or system activity while scheduling the upgrade.
This path traversal flaw differs from the earlier FortiMail file-write vulnerability. It also differs from the separate FortiMail command-injection and SQL-injection records, CVE-2026-126148 and CVE-2026-126164.
For another path traversal issue involving sensitive data exposure, review IBM Optim CVE-2026-17466.
Who is affected
Which FortiMail Versions Are Affected by CVE-2026-126147?
Fortinet lists four affected release lines in FG-IR-26-199. The vendor's table supplies the following affected ranges and solutions for this path traversal 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 updated FortiMail Cloud firmware on October 5, 2026, to 7.6.7 GA or 8.0.2 GA. According to the advisory, FortiMail Cloud customers need take no action for this issue.
The advisory lists no virtual patch. Teams managing their own FortiMail deployments should verify installed versions and follow the corresponding vendor solution.
The vulnerability management guide explains how to prioritize remediation work. The Fortinet November advisory overview provides context for the separate flaws.
Timeline
- 2026-10-05
Fortinet says it remediated FortiMail Cloud by updating all firmware to 7.6.7 GA or 8.0.2 GA.
- 2026-11-10
Fortinet initially published FG-IR-26-199 and marked Known Exploited as No.
- 2026-11-11
NVD published the Fortinet-sourced CVE-2026-126147 record.
What to do
-
Inventory FortiMail deployments
Record installed versions and distinguish self-managed FortiMail from FortiMail Cloud. Compare each self-managed installation with Fortinet's four affected release lines.
-
Apply Fortinet's fixed release
Upgrade 8.0.0 through 8.0.1 to 8.0.2 or above, 7.6.0 through 7.6.6 to 7.6.7 or above, and 7.4.0 through 7.4.8 to 7.4.9 or above. Migrate 7.2 deployments to a fixed release.
-
Review exposure and telemetry
Brandefense recommends limiting API access to intended systems and reviewing relevant logs for unexpected administrative or system activity. Treat anomalies as investigation leads, not proof of this specific CVE.
-
Verify remediation
Confirm the installed release after maintenance and recheck Fortinet PSIRT FG-IR-26-199 for changes to fixes or 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-126147 in Brandefense Atlas
The Atlas record of CVE-2026-126147: 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-126147?
It is a FortiMail path traversal flaw (CWE-22). Fortinet says crafted requests may allow unauthenticated execution of unauthorized code or commands.
Which FortiMail versions require an upgrade?
Fortinet lists 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, 7.4.0 through 7.4.8, and all 7.2 versions as affected.
What should FortiMail 7.2 users do?
Fortinet lists every 7.2 version as affected and directs users to migrate to a fixed release.
Do FortiMail Cloud customers need to update for this flaw?
Fortinet says it remediated FortiMail Cloud on October 5, 2026, and that cloud customers need take no action for this issue.
Is CVE-2026-126147 known to be exploited?
Fortinet marked Known Exploited as No at publication. The CVE was absent from CISA KEV catalog version 2026.11.10; those statements are dated.
Sources
- FG-IR-26-199: Improper limitation of a pathname to a restricted directoryFortinet PSIRT
- CVE-2026-126147National Vulnerability Database
- Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency