Is CVE-2026-126160 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-126160 being exploited in the wild.

How severe is CVE-2026-126160?

High severity, with a CVSS score of 8.2, published 11 November 2026.

Which products and versions are affected?

Fortinet FortiMail 7.2 (all versions), 7.4.0-7.4.8, 7.6.0-7.6.6, 8.0.0-8.0.1.

Is there a fix for CVE-2026-126160?

Yes: fixed in FortiMail 7.4.9 or above, 7.6.7 or above, 8.0.2 or above; FortiMail 7.2 customers must 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-126160 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-126160?

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.

CVE-2026-126160: Fortinet FortiMail improper authentication in quarantine release

CVE-2026-126160 · Severity: high · CVSS 8.2 · Published 2026-11-11

FortiMail is an email security appliance that manages and quarantines suspicious messages. An unauthenticated attacker can bypass authentication controls to release or delete quarantined messages from any user's mailbox, potentially exposing sensitive emails or disrupting email operations across the organization.

Technologies: Fortinet FortiMail. Vendors: Fortinet.

Quick answers

Is CVE-2026-126160 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-126160 being exploited in the wild.
How severe is CVE-2026-126160?: High severity, with a CVSS score of 8.2, published 11 November 2026.
Which products and versions are affected?: Fortinet FortiMail 7.2 (all versions), 7.4.0-7.4.8, 7.6.0-7.6.6, 8.0.0-8.0.1.
Is there a fix for CVE-2026-126160?: Yes: fixed in FortiMail 7.4.9 or above, 7.6.7 or above, 8.0.2 or above; FortiMail 7.2 customers must 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-126160 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-126160?: 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 customers must migrate to a fixed release

Technical details

An improper authentication vulnerability (CWE-287) in the FortiMail quarantine release API allows unauthenticated attackers to craft malicious quarantine release requests and escalate privileges to access and manipulate quarantined messages for arbitrary mailboxes. The vulnerability affects versions 7.2 through 8.0.1 and requires no user interaction or network adjacency—only network access to the FortiMail API endpoint. A successful exploit grants an attacker the ability to release or delete quarantined emails without authentication.

Affected products

Fortinet FortiMail 7.2 (all versions), 7.4.0-7.4.8, 7.6.0-7.6.6, 8.0.0-8.0.1

Timeline

2026-11-10: disclosed
2026-10-05: patched: FortiMail Cloud updated to v7.6.7 GA or v8.0.2 GA

References

https://fortiguard.fortinet.com/psirt/FG-IR-26-212

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.