Fortinet FortiMail 8.0.0: path traversal

Fortinet FortiMail

A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiMail 8.0.0 through 8.0.1, FortiMail 7.6.0 through 7.6.6, FortiMail 7.4.0 through 7.4.8, FortiMail 7.2 all versions may allow an unauthenticated attacker to execute unauthorized code or commands via crafted requests.

Do this now

Upgrade FortiMail to 8.0.2, 7.6.7, or 7.4.9 to close the path traversal flaw.

Who should check: teams running VPN & firewalls

Fix it

FortiMail

On 7.4.xUpgrade to FortiMail 7.4.9
On 7.6.xUpgrade to FortiMail 7.6.7
On 8.0.xUpgrade to FortiMail 8.0.2
On 7.2.xNo fix on 7.2.x: migrate to a fixed release

FortiMail Cloud: no customer action required (FG-IR-26-199) (vendor advisory)

First seen: 12 Nov 2026
Last update: 12 Nov 2026, 04:18 UTC
Fixed in: 8.0.2
7.6.7
7.4.9
Identifiers: CVE-2026-126147
CVSS: 9.8
Source: news
On the menu as: VPN & firewalls

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## Fortinet FortiMail 8.0.0: path traversal
Severity: critical. Patch status: patched.
Affected: Fortinet FortiMail
Fixed in: 8.0.2, 7.6.7, 7.4.9
Ids: CVE-2026-126147

A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiMail 8.0.0 through 8.0.1, FortiMail 7.6.0 through 7.6.6, FortiMail 7.4.0 through 7.4.8, FortiMail 7.2 all versions may allow an unauthenticated attacker to execute unauthorized code or commands via crafted requests.

## Steps
1. This touches infrastructure (vpn-edge). Look in terraform, ansible, cloud-init, Dockerfiles and docs for the product and version we run. If it isn't in the repo, say so and list what a human should check on the box.
2. Fix by release line: FortiMail: 8.0.x → 8.0.2; 7.6.x → 7.6.7; 7.4.x → 7.4.9; 7.2.x → no fix on 7.2.x: migrate to a fixed release.

## Fix by release line
| Line | State | Fix | Until then |
|---|---|---|---|
| FortiMail 8.0.x | fixed | 8.0.2 | — |
| FortiMail 7.6.x | fixed | 7.6.7 | — |
| FortiMail 7.4.x | fixed | 7.4.9 | — |
| FortiMail 7.2.x | migrate | move to 7.4.9 | restrict network access to it |

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve("CVE-2026-126147") for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://fortiguard.fortinet.com/psirt/FG-IR-26-199 https://nvd.nist.gov/vuln/detail/CVE-2026-126147
https://pwned.coffee/i/fortinet-fortimail-8-0-0-path-traversal-cve-2026-126147

Timeline

12 Nov 2026, 04:18 UTC
Fix status: unknown → patched.
12 Nov 2026
First reported.

Receipt

Exploitation: No known exploitation
Fix by release line: Product Affected Fixed in Source
FortiMail <= 8.0.1 8.0.2 Vendor advisory checked 12 Nov
FortiMail <= 7.6.6 7.6.7 Vendor advisory checked 12 Nov
FortiMail <= 7.4.8 7.4.9 Vendor advisory checked 12 Nov
FortiMail 7.2.0 to now no fix on 7.2.x: migrate to a fixed release Vendor advisory checked 12 Nov
Score: CVSS 9.8 (critical). CVSS 3.1 9.8 (CNA fortinet) for CVE-2026-126147
Last checked: 13 Nov 2026, 16:26 UTC

Product	Affected	Fixed in	Source
FortiMail	<= 8.0.1	8.0.2	Vendor advisory checked 12 Nov
FortiMail	<= 7.6.6	7.6.7	Vendor advisory checked 12 Nov
FortiMail	<= 7.4.8	7.4.9	Vendor advisory checked 12 Nov
FortiMail	7.2.0 to now	no fix on 7.2.x: migrate to a fixed release	Vendor advisory checked 12 Nov

Sources: KEV – CVE record ✓ Vendor ✓

Sources

Follow on X

Totalone very hot coffee