Introduction
The quarantine is where an email security gateway puts the messages it has decided users should not receive yet: suspected spam, phishing, and malware. In FortiMail, a flaw in how the API authorizes quarantine actions means an unauthenticated attacker may be able to release or delete those held messages for any mailbox on the system, not just their own.
Fortinet tracks the issue as CVE-2026-126159 in advisory FG-IR-26-211, published November 10, 2026, with the NVD entry following on November 11, 2026. It carries a CVSS v3.1 base score of 7.5 (High). Fixed builds exist for the 8.0, 7.6 and 7.4 branches. The 7.2 branch receives no fix at all, so 7.2 deployments need to migrate to another branch.
FortiMail is Fortinet's email security product. Fortinet's datasheet describes it as protecting against spam, phishing, malware, impersonation and business email compromise, using FortiGuard Labs threat intelligence and integrating with the Fortinet Security Fabric. Fortinet itself is a large network security vendor (its March 2026 investor presentation cites more than 50% global firewall shipment share, per 650 Group), though that figure describes firewalls and says nothing about how many FortiMail systems are exposed.
Technical information
Root cause
Fortinet classifies the bug as CWE-639, Authorization Bypass Through User Controlled Key, and identifies the affected component as the API. MITRE describes this weakness class as an authorization failure in which a key supplied by the user identifies another user's record or data, and the system acts on it without confirming the requester is entitled to that record.
Fortinet's description of the FortiMail bug is specific about the outcome: a crafted quarantine release request may allow an unauthenticated attacker to release or delete quarantined messages for arbitrary mailboxes. The server appears to trust a reference carried in the request (such as a mailbox, recipient or message identifier) when deciding which quarantined messages to act on, rather than binding the action to an authorization context it controls.
MITRE's general CWE-639 discussion often describes an authenticated user reaching across to another user's data. This FortiMail advisory goes further and explicitly describes an unauthenticated attacker, and the CVSS vector agrees with PR:N.
FortiMail is closed source, and Fortinet has not published the vulnerable endpoint, parameter names, identifier format, or request body. No vulnerable code is public, so we do not reproduce or approximate any here.
CVSS breakdown
The published base vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.
- Attack Vector: Network
- Attack Complexity: Low (no special conditions are scored)
- Privileges Required: None (no authentication is needed)
- User Interaction: None (no victim action is required)
- Scope: Unchanged
- Confidentiality: None (the score does not assign mailbox content disclosure)
- Integrity: High (unauthorized release or deletion of quarantined messages is the scored impact)
- Availability: None
Fortinet's extended vector also includes E:P. Under the FIRST CVSS v3.1 specification, that is the Proof of Concept exploit code maturity value: code or a technique exists but is not functional in all situations and may need substantial modification by a skilled attacker. That value is not evidence of attacks in the wild, and the advisory does not link to any public exploit.
The record also makes no claim of message content disclosure, account takeover, remote code execution, or full appliance compromise.
Attack flow
Based solely on the advisory, the attack reduces to the following sequence:
- The attacker has network access to the FortiMail API that handles quarantine release requests. No credentials are required.
- The attacker sends a crafted quarantine release request that references quarantined messages belonging to a mailbox the attacker does not own.
- FortiMail fails to verify that the requester is authorized for that mailbox and processes the request.
- The targeted quarantined messages are released or deleted.
The practical consequence is a loss of integrity over the quarantine. Messages FortiMail deliberately held back can be released without the owner's or an administrator's decision, and held messages can be deleted before anyone reviews them.
The advisory does not state how an attacker obtains or constructs the target identifier, whether specific deployment settings are necessary, or which exact requests are involved. Because of those gaps, the public record is enough to prioritize patching but not enough to build a reliable exploit or a CVE-specific detection signature.
Threat context
Fortinet marks CVE-2026-126159 as "Known Exploited: No". No threat actor, campaign, ransomware operation, victim, or indicator set is named, and the TridentStack record notes that EPSS data is unavailable. That label reflects the available disclosure. It does not prove that exploitation has never occurred.
Patch information
Fortinet fixed CVE-2026-126159 in FortiMail firmware and documented the fix in PSIRT advisory FG-IR-26-211, first released November 10, 2026. Because FortiMail is a closed-source appliance, there is no public commit, source diff, or code snippet. The only public evidence of the fix is the list of fixed builds in the advisory.
- FortiMail 8.0: vulnerable 8.0.0 through 8.0.1, fixed in 8.0.2 or later.
- FortiMail 7.6: vulnerable 7.6.0 through 7.6.6, fixed in 7.6.7 or later.
- FortiMail 7.4: vulnerable 7.4.0 through 7.4.8, fixed in 7.4.9 or later.
- FortiMail 7.2: all versions vulnerable (NVD lists 7.2.0 through 7.2.9), with no fix on this branch. Move to a fixed release on a supported branch.
The 7.2 row is the one that changes planning. Fortinet is not backporting the fix to 7.2, so no 7.2.x build will be safe. Fixing a 7.2 system means a major version upgrade to 7.4.9+, 7.6.7+ or 8.0.2+, not a maintenance update. Follow the documented upgrade path in the target release's notes, since jumping across major versions may require intermediate builds.
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 action. That date also means the fixed builds were shipping roughly five weeks before the advisory and CVE were published. The Cloud statement says nothing about appliances or VMs you operate yourself, and those still need the upgrade.
What the fix logically has to change
The following is general background on remediating CWE-639, not a description of Fortinet's code, which is not public. A correct fix ties the release or delete action to something the server controls rather than a value the client sends. Typical approaches include:
- Checking that the authenticated session, or a signed, unguessable, single-use token, belongs to the mailbox that owns the message.
- Rejecting requests where the mailbox or message reference does not match that token.
- Refusing release or delete actions that carry no valid authorization context at all.
What Fortinet has not published
- No virtual patch. The advisory marks "Virtual Patch: No", so no FortiGuard IPS signature blocks exploitation in the interim, and no workaround is provided. Upgrading the firmware is the only vendor fix.
- No matching release note entry. The FortiMail 8.0.2 release notes do not list this CVE or the quarantine authorization change. The closest resolved issue is Bug ID 1319365, about duplicate emails being released from the system quarantine, and nothing links it to this CVE. The advisory is the authoritative record that 8.0.2, 7.6.7 and 7.4.9 contain the fix.
One secondary CVE page states it found no published remediation. Fortinet's own advisory, which lists fixed releases, is the authoritative source here.
Upgrade precautions
The FortiMail 7.6.7 release notes list several precautions worth following:
- Back up the configuration and other stored data before upgrading or downgrading.
- Clear the browser cache before logging in after a firmware upgrade or downgrade.
- Verify that the displayed build and version numbers match the loaded firmware image.
- Consult Fortinet Technical Support before considering a downgrade. The notes say downgrading is generally not recommended or supported.
Who found it
Fortinet's own Product Security team found the issue internally. The advisory credits Gwendal Guegniaud, working with the frontier AI model Claude Mythos. The credit acknowledges discovery and does not attribute the issue to any attacker.
Affected systems and versions
- FortiMail 8.0: 8.0.0 through 8.0.1
- FortiMail 7.6: 7.6.0 through 7.6.6
- FortiMail 7.4: 7.4.0 through 7.4.8
- FortiMail 7.2: all versions (NVD lists 7.2.0 through 7.2.9)
- FortiMail Cloud: remediated by Fortinet on October 5, 2026, with no customer action required
The advisory does not identify a specific configuration that must be enabled for exploitation. The vulnerable component is the FortiMail API handling quarantine release requests.
Vendor security history
Fortinet's published vulnerability policy states that it evaluates issues with CVSS 3.1, publishes details of resolved vulnerabilities, and may issue out-of-cycle advisories for critical issues. The company also describes a development process that includes static and dynamic application testing, software composition analysis, fuzzing, penetration testing and manual code audits. Those are the vendor's own descriptions, not independent assurance.
FortiMail has recent history with exploited vulnerabilities, but of a different kind. Advisory FG-IR-26-175 covers CVE-2026-104286, an unauthenticated arbitrary file write involving path traversal and NULL-byte handling. Fortinet reported exploitation in the wild, and CISA added it to the Known Exploited Vulnerabilities catalog. That advisory includes its own workarounds and indicators, including controls involving IBE and webmail access. Those belong to CVE-2026-104286 and should not be applied as if they address CVE-2026-126159.
Keep the two issues separate. Exploitation evidence for CVE-2026-104286 does not transfer to this quarantine bypass, and the lack of confirmed exploitation for CVE-2026-126159 does not change Fortinet's upgrade instructions.
References
- NVD: CVE-2026-126159
- CVE Record: CVE-2026-126159
- Fortinet PSIRT Advisory FG-IR-26-211
- FortiMail 8.0.2 Release Notes: Resolved Issues
- FortiMail 8.0.2 Release Notes: What's Changed
- FortiMail 7.6.7 Release Notes (PDF)
- MITRE CWE-639: Authorization Bypass Through User Controlled Key
- FIRST CVSS v3.1 Specification
- Fortinet PSIRT Advisory FG-IR-26-175 (CVE-2026-104286)
- CISA: Adds One Known Exploited Vulnerability to Catalog
- CISA Known Exploited Vulnerabilities Catalog
- HKCERT: Fortinet Products Multiple Vulnerabilities
- TridentStack: CVE-2026-126159
- Fortinet Security Vulnerability Policy
- Fortinet: Secure Product Development and Responsible Disclosure
- FortiMail Data Sheet
- About Fortinet
- Fortinet Investor Relations Presentation, March 2026



