Quick answers
- Is CVE-2026-126157 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126157 being exploited in the wild.
- How severe is CVE-2026-126157?
- Critical severity, with a CVSS score of 9.1, published 11 November 2026.
- Which products and versions are affected?
- Fortinet FortiMail 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, 7.4.0 through 7.4.8, 7.2 all versions, 7.0 all versions.
- Is there a fix for CVE-2026-126157?
- Yes: fixed in FortiMail 8.0.2 or above, 7.6.7 or above, 7.4.9 or above. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126157 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-126157?
- 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 8.0.2 or above, 7.6.7 or above, 7.4.9 or above
Technical details
A missing authentication vulnerability (CWE-306) in the FortiMail API allows unauthenticated attackers to access arbitrary user email accounts via crafted HTTP requests. The vulnerability affects multiple versions across FortiMail 8.0, 7.6, 7.4, 7.2, and 7.0 product lines. Exploitation requires only network access to the affected API endpoint and yields full access to victim email accounts.
Affected products
- Fortinet FortiMail 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, 7.4.0 through 7.4.8, 7.2 all versions, 7.0 all versions
Timeline
- 2026-11-10: disclosed: PSIRT advisory published
- 2026-10-05: patched: FortiMail Cloud remediated