Automated Threat Modeling

Brief Summary: FortiMail CVE-2026-126160 Improper Authentication in Quarantine Release Control

A brief summary of CVE-2026-126160, an improper authentication flaw in FortiMail quarantine release control that may let an unauthenticated attacker release or delete quarantined messages for arbitrary mailboxes. Includes affected versions and Fortinet's fixed release paths.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Brief Summary: FortiMail CVE-2026-126160 Improper Authentication in Quarantine Release Control

Introduction

A flaw in FortiMail's quarantine release handling may let an unauthenticated attacker release or delete quarantined messages belonging to arbitrary mailboxes. For organizations that depend on FortiMail quarantine to hold suspicious mail away from users, this means a security decision made by the gateway could be reversed or erased by someone who never logged in.

FortiMail is Fortinet's email security product, offered as hardware appliances, virtual machines and a hosted cloud service, and able to run in Gateway, Transparent or Server mode. Fortinet reports that it was named a Challenger in the 2025 Gartner Magic Quadrant for Email Security, which is a vendor-published account of an analyst assessment rather than a market share figure. FortiMail sits directly in the mail flow and integrates with other Fortinet and third-party components to share indicators of compromise, so the integrity of its quarantine decisions affects what ultimately lands in user inboxes.

The CVE record lists the vendor as unknown, but NVD identifies Fortinet as the CVE source and scoring authority, and the primary advisory is FortiGuard FG-IR-26-212. Fortinet published the advisory on November 10, 2026. NVD published the record on November 11, 2026.

Technical Information

Root cause

Fortinet titles the advisory "Improper authentication in releasecontrol" and classifies the weakness as CWE-287, Improper Authentication. The advisory lists the component as API, the attack type as unauthenticated and the impact as improper access control.

The releasecontrol component is FortiMail's quarantine release logic, which processes requests to release or delete quarantined messages. In vulnerable builds, a crafted quarantine release request could act on messages in arbitrary mailboxes without the server establishing that the requester was entitled to perform that action. The authentication boundary that should bind a release or delete operation to an authorized user or mailbox owner was not enforced correctly.

FortiMail is closed source. Fortinet has not published the request format, the exact endpoint, vulnerable parameter names, a patch diff or a full exploitation sequence. The component name releasecontrol should not be treated as a confirmed URL path, and we do not reproduce any code here because none has been made public.

Why quarantine control is the affected boundary

Fortinet's administration guide describes quarantine reports that let users release or delete their own quarantined messages, and quarantine control accounts that receive release and delete commands. The product can also be configured to rescan messages before release. These are documented product features rather than additional confirmed details of this bug. They do explain the target, because CVE-2026-126160 exposes operations that are meant to be scoped to a particular user or mailbox to an unauthenticated party.

CVSS assessment

NVD reproduces the Fortinet CNA vector and notes that it has not provided its own separate assessment.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
  • AV:N: reachable over the network
  • AC:L: low attack complexity
  • PR:N: no prior privileges required
  • UI:N: no user interaction required
  • S:U: scope unchanged
  • C:N: no confidentiality impact assigned
  • I:H: high integrity impact (unauthorized release of quarantined mail)
  • A:L: low availability impact (unauthorized deletion of quarantined mail)

The base score is 8.2 (High). Fortinet also publishes a temporal score of 7.8, with E:P, RL:O and RC:C in its temporal vector.

Attack flow

Based on the advisory and NVD description, the documented attack path is:

  1. The attacker has network access to a FortiMail instance running an affected release. No account or prior privileges are required.
  2. The attacker sends a crafted quarantine release request targeting messages in a mailbox they do not own.
  3. Because releasecontrol does not properly authenticate the request, FortiMail accepts it, effectively escalating the attacker to the privileges needed to act on that mailbox's quarantine.
  4. The attacker releases quarantined messages into the target mailbox, or deletes them.

The practical consequences follow from the CVSS impacts. Mail that FortiMail deliberately held back can be pushed to recipients, and quarantined evidence can be removed before an administrator or user reviews it.

What the sources do not establish

The advisory and NVD description do not claim shell access, root privileges, arbitrary file access or remote code execution on the appliance. The vector assigns no confidentiality impact, so reading or exfiltrating quarantined content is not part of the documented impact either. We keep the scope to unauthorized quarantine release and deletion.

Exploitation status

As reviewed on November 11, 2026, Fortinet's advisory lists "Known Exploited: No", and VulDB shows "KEV: no". No threat actor, campaign or indicators of compromise are associated with this CVE in the reviewed sources.

The temporal E:P value is easy to misread. Under CVSS v3.1, Proof of Concept means exploit code or an attack demonstration exists that is not practical for most systems and may need substantial modification by a skilled attacker. It describes exploit maturity, not observed attacks, and no runnable exploit or reproduction request has been published.

Belgium's CCB has warned about CVE-2026-104286, a different FortiMail vulnerability that it reports as actively exploited and included in the CISA KEV catalog. That exploitation status, and any associated indicators, do not carry over to CVE-2026-126160.

Patch Information

Fortinet fixed this flaw in new firmware. Because FortiMail is closed source, there is no public commit, diff or code snippet. Everything below comes from FG-IR-26-212 and the CVE and NVD records that reference it.

The fix belongs on the server side, where release and delete requests handled by releasecontrol now have to pass a real authentication check before they are accepted. Fortinet has not said exactly how that check works. It could be stronger request or token validation, or binding each request to the owner of the mailbox, but any specific mechanism should be treated as unconfirmed. What is confirmed is that the fix ships only as a firmware update.

Fixed releases by branch

  • FortiMail 8.0: 8.0.0 through 8.0.1 vulnerable, fixed in 8.0.2 or above
  • FortiMail 7.6: 7.6.0 through 7.6.6 vulnerable, fixed in 7.6.7 or above
  • FortiMail 7.4: 7.4.0 through 7.4.8 vulnerable, fixed in 7.4.9 or above
  • FortiMail 7.2: all versions vulnerable, no 7.2 fix, migrate to a fixed branch

Fortinet is not releasing a 7.2 patch, and the advisory instructs 7.2 customers to "Migrate to a fixed release". In practice a 7.2 deployment has to move to the 7.4, 7.6 or 8.0 branch at or above the versions listed. This is a cross-branch upgrade, not a minor update, so plan for it accordingly.

FortiMail Cloud

Fortinet states it remediated the hosted service on October 5, 2026 by moving all FortiMail Cloud firmware to v7.6.7 GA or v8.0.2 GA. Cloud customers do not need to take any action. The advisory went public on November 10, 2026, so the hosted service was patched roughly five weeks before disclosure. The same CVE therefore requires customer action on appliances and VMs while already being resolved by the provider in the cloud.

Other patch facts

  • The advisory's Virtual Patch field reads "No". A FortiGuard IPS signature in front of the appliance is not a substitute, and the firmware update is required.
  • The advisory does not provide a workaround. Fortinet's broader hardening guidance (restricting administrative interfaces to trusted IPs, strong unique credentials, MFA, log monitoring) is general advice and explicitly does not replace upgrading. It is not a demonstrated fix for this unauthenticated quarantine API flaw.
  • The CNA vector includes RL:O (Remediation Level: Official Fix), and the CVE record's solution list gives 8.0.2, 7.6.7 and 7.4.9 as the minimum fixed versions.
  • Fortinet's Product Security team found the issue internally, credited to Gwendal Guegniaud using the AI model Claude Mythos. The fix shipped in Fortinet's November 2026 PSIRT cycle.

Verifying the fix

With no code to inspect, verification is a version check. An appliance or VM counts as fixed only if its firmware is at or above the fixed release for its branch: 8.0.2, 7.6.7 or 7.4.9. Any 7.2.x build remains vulnerable regardless of its patch level.

Affected Systems and Versions

  • FortiMail 8.0: versions 8.0.0 through 8.0.1
  • FortiMail 7.6: versions 7.6.0 through 7.6.6
  • FortiMail 7.4: versions 7.4.0 through 7.4.8
  • FortiMail 7.2: all versions

These apply to customer-maintained appliances and virtual machines. FortiMail Cloud is listed as already remediated by Fortinet.

NVD and Fortinet represent the 7.2 range differently. NVD's affected product table lists FortiMail 7.2.0 through 7.2.9, while both NVD's narrative description and Fortinet's advisory say all 7.2 versions. Fortinet's broader statement is the safer basis for remediation decisions.

Vendor Security History

Fortinet's PSIRT handles vulnerability intake, investigation and public reporting, and its published policy describes severity-based prioritization and fixes that may require upgrading to supported releases. For this CVE the response included fixed releases across three branches and a completed cloud remediation ahead of disclosure, following internal discovery.

Fortinet products have a history of serious preauthentication issues. In its analysis of CVE-2023-27997, a preauthentication heap buffer overflow in FortiOS SSL VPN, Fortinet said the flaw may have been exploited in a limited number of cases and advised immediate upgrades. That disclosure followed a proactive SSL VPN code audit prompted by an earlier incident involving CVE-2022-42475. Fortinet also explicitly declined to link CVE-2023-27997 to the Volt Typhoon campaign, identifying CVE-2022-40684 as a primary initial access vulnerability in that context. Within FortiMail itself, CCB has reported CVE-2026-104286 as actively exploited. None of this history identifies any actor exploiting CVE-2026-126160.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization