Quick answers
- Is CVE-2026-126147 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126147 being exploited in the wild.
- How severe is CVE-2026-126147?
- Critical severity, with a CVSS score of 9.8, published 11 November 2026.
- Which products and versions are affected?
- Fortinet FortiMail 7.2 all versions, 7.4.0 through 7.4.8, 7.6.0 through 7.6.6, 8.0.0 through 8.0.1.
- Is there a fix for CVE-2026-126147?
- Yes: fixed in FortiMail 7.4.9 or above, 7.6.7 or above, 8.0.2 or above; FortiMail 7.2 migrate to a fixed release. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126147 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-126147?
- Check whether you run Fortinet FortiMail at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: FortiMail 7.4.9 or above, 7.6.7 or above, 8.0.2 or above; FortiMail 7.2 migrate to a fixed release
Technical details
A path traversal vulnerability (CWE-22) in the FortiMail API allows unauthenticated remote attackers to escape directory restrictions via crafted requests, enabling unauthorized code or command execution. The flaw affects versions 7.2 (all), 7.4.0–7.4.8, 7.6.0–7.6.6, and 8.0.0–8.0.1. No authentication is required to exploit this network-accessible vulnerability.
Affected products
- Fortinet FortiMail 7.2 all versions, 7.4.0 through 7.4.8, 7.6.0 through 7.6.6, 8.0.0 through 8.0.1
Timeline
- 2026-11-10: disclosed
- 2026-10-05: patched: FortiMail Cloud remediated by updating to v7.6.7 GA or v8.0.2 GA