Introduction
An unauthenticated attacker with network access to a vulnerable FortiMail deployment may be able to take over the account an external recipient uses to read encrypted mail, without credentials and without any user interaction. Fortinet rates CVE-2026-126156 as Critical with a CVSS v3.1 base score of 9.1, and the fixed firmware shipped roughly five weeks before the advisory went public on 10 November 2026.
FortiMail is Fortinet's email security product, delivered as hardware appliances, virtual machines, and the managed FortiMail Cloud service. Fortinet reports more than 900,000 customers and over 130 products across its portfolio, although those figures describe the company as a whole rather than the FortiMail install base. FortiMail's Identity Based Encryption (IBE) feature is how organizations deliver encrypted messages to outside recipients, and this flaw affects the accounts those recipients use.
Technical information
Root cause: CWE-639 in the API component
Fortinet classifies the issue as CWE-639, Authorization Bypass Through User Controlled Key, in the FortiMail API component. The advisory's description is precise but brief: an unauthenticated remote attacker may take over an arbitrary IBE recipient account via crafted HTTP requests.
MITRE describes CWE-639 as an authorization failure in which changing a key that identifies a record allows access to another user's data. The same pattern is commonly called Insecure Direct Object Reference (IDOR) or Broken Object Level Authorization (BOLA). It is a horizontal authorization failure: the server trusts an identifier supplied by the client to decide which account a request acts on, without verifying that the requester actually owns that identifier.
MITRE's general description assumes an attacker who is likely already authenticated. Fortinet's advisory explicitly describes an unauthenticated attacker, and the CVSS vector agrees (PR:N). We should not import a login requirement from the generic CWE text that the actual vulnerability does not have.
The advisory does not identify the HTTP method, the URL, the account identifier being manipulated, session behavior, or the specific implementation defect. Any claim about the exact vulnerable parameter would be speculation.
Why IBE recipient accounts matter
Fortinet's administration guide explains how IBE works on FortiMail:
- IBE uses identities such as email addresses to calculate encryption keys.
- FortiMail encrypts a message with a public key generated from the recipient's email address and sends a notification containing access instructions.
- A new recipient must register before reading the message, and messages are decrypted automatically when opened on FortiMail.
- External IBE users access secure messages through the notification link, while internal protected domain users can also use webmail login.
The recipient account is the access control gate in front of encrypted mail stored on FortiMail. If an attacker can take control of that account, the strength of the encryption is largely beside the point, because the platform decrypts messages for whoever holds the account. Neither the advisory nor the IBE documentation suggests the underlying encryption algorithm is broken. The failure is in the authorization around the account.
Reading the CVSS vector
Fortinet, acting as CNA, supplied this vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- AV:N Network attack vector
- AC:L Low attack complexity
- PR:N No privileges required
- UI:N No user interaction
- S:U Scope unchanged
- C:H / I:H High confidentiality and integrity impact
- A:N No availability impact assigned
The vector supports concern about the confidentiality and integrity of recipient accounts. It does not describe denial of service or code execution on the appliance. NVD currently displays the NIST base score as unavailable and lists the record status as Received, so 9.1 is the vendor's assessment rather than an independent NIST score.
Attack flow, as disclosed
Based strictly on the advisory and the CVSS vector, the attack sequence looks like this:
- The attacker reaches the FortiMail HTTP interface that serves the affected API component over the network.
- The attacker sends crafted HTTP requests without authenticating and without needing any action from a victim.
- The requests rely on a user-controlled key that identifies an IBE recipient account, and FortiMail fails to verify that the requester is authorized to act on that account.
- The attacker takes over the targeted IBE recipient account, and the advisory describes this as possible for an arbitrary recipient.
The specific endpoint, identifier, and payload are unpublished, and Fortinet has intentionally withheld them.
Exploitation status
Fortinet's advisory states Known Exploited: No, and the bug was found internally. The calculator link in the advisory includes the temporal parameter E:P, while the explicit exploitation status remains No. The sources we reviewed do not identify a publicly available exploit. HKCERT's 11 November 2026 bulletin lists this CVE among many Fortinet issues under a bulletin-level Medium Risk rating, with collective effects such as remote code execution and denial of service. Those collective effects belong to other CVEs in the bulletin. For this CVE, Fortinet's Critical rating and account takeover description are the authoritative characterization.
Patch information
FortiMail is closed source, so there is no public commit, diff, or patch file. The authoritative record is Fortinet PSIRT advisory FG-IR-26-208, published 10 November 2026, which NVD lists as the only reference for this CVE.
Fixed releases by branch
- FortiMail 8.0 (8.0.0 through 8.0.1): upgrade to 8.0.2 or later (build 263)
- FortiMail 7.6 (7.6.0 through 7.6.6): upgrade to 7.6.7 or later (build 858)
- FortiMail 7.4 (7.4.0 through 7.4.8): upgrade to 7.4.9 or later (build 630)
- FortiMail 7.2 (all 7.2.x): no 7.2 fix exists. Fortinet says to migrate to a fixed release, and its hardening announcement says to move to the 7.4 branch or later
- FortiMail Cloud: Fortinet remediated the hosted service on 5 October 2026, and no customer action is required for this issue
The advisory lists Virtual Patch: No. There is no signature-based stopgap and no published workaround, so a firmware upgrade is the only vendor fix. For 7.2 owners, moving off 7.2 is a branch upgrade rather than a simple patch install, so plan it accordingly.
NVD's structured affected product data bounds 7.2 at 7.2.0 through 7.2.9, while both the NVD description and the vendor advisory say all 7.2 versions are affected. That discrepancy lives in the published records. It is not evidence that any 7.2 build is fixed. Follow the vendor's migration instruction.
Fixes shipped weeks before the advisory
These builds were part of a coordinated security hardening release covering bugs found through Fortinet's frontier AI-assisted testing programme. According to a third-party review of Fortinet's change logs, FortiMail 7.6.7 was released on 2 October 2026, and 7.4.9 and 8.0.2 on 3 October 2026, about five weeks before the advisory. Fortinet withheld technical details on purpose. Its CISO explained that the gap gives customers time to upgrade because "once updates are public, the fixes themselves reveal where changes were made" and attackers can diff patches quickly. In practice, an appliance already running 8.0.2, 7.6.7, or 7.4.9 was protected before the CVE number existed.
What the fix most likely changes (inference)
Fortinet has not said which IBE handler or parameter changed. For the CWE-639 bug class in general, the usual fix is to:
- bind the identity used for an action to something the server issued and can verify, such as an authenticated session or a signed, single-use token, rather than a value the client supplies;
- reject requests where the supplied key does not match the verified identity.
MITRE's developer guidance is similar: verify authorization for every record access and avoid externally controllable lookup keys, or detect tampering with them. Treat this as a description of the bug class, not confirmed details of FortiMail's code, and not a customer configuration fix.
The release notes do not list this fix
The public FortiMail 8.0.2 release notes include a "no longer vulnerable" table that lists only CWE-22, CWE-89, CWE-321, CWE-522, and CWE-1050 bug IDs. There is no CWE-639 or IBE entry, and the notes state the list is incomplete. You cannot confirm this fix from the release notes. Use the advisory's version table and check the running firmware version and build number on each appliance.
Upgrade precautions
The 8.0.2 release notes instruct administrators to back up the configuration and other stored data before upgrading or downgrading, and to clear the browser cache after a firmware change and before logging in to the web UI. They also state that firmware downgrading is generally not recommended or supported. Intermediate versions in the published upgrade path are stepping stones, not substitutes for the fixed versions listed in the advisory.
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
The affected configuration is FortiMail appliance and VM deployments where the IBE recipient account functionality is in use, since the documented outcome is takeover of IBE recipient accounts. FortiMail Cloud is not affected for customers after Fortinet's 5 October 2026 remediation. An installation on 7.6.6 remains vulnerable, while 7.6.7 is fixed. For 7.2, no release within the branch resolves the issue.
Vendor security history
Fortinet credits Gwendal Guegniaud of its Product Security team, using the frontier AI model Claude Mythos, with discovering this vulnerability. The company's product security commitment document describes a Secure Product Development Lifecycle with threat modeling, application testing, fuzzing, AI-assisted code auditing, and internal and independent penetration testing, and states that approximately 60% of vulnerabilities discovered in 2025 were identified internally. Fortinet publishes vulnerability advisories monthly on the second Tuesday. These are vendor-reported claims.
Government reporting confirms serious exploitation elsewhere in the portfolio:
- December 2022: CISA reported exploitation of CVE-2022-42475, a FortiOS heap-based buffer overflow that could allow control of an affected system.
- April 2025: CISA described a malicious file created following exploitation of earlier FortiGate vulnerabilities, potentially allowing read-only access to device files including configurations, with exploitation requiring SSL VPN to be enabled. Fortinet contacted identified affected customers with mitigation guidance.
- 1 October 2026: CISA added CVE-2026-104286, a FortiMail path traversal vulnerability, to its Known Exploited Vulnerabilities Catalog based on evidence of active exploitation.
The FortiMail KEV entry shows real attacker interest in the product, but it concerns a different vulnerability and does not establish exploitation or attribution for CVE-2026-126156.
References
- NVD: CVE-2026-126156
- CVE Record: CVE-2026-126156
- Fortinet PSIRT Advisory FG-IR-26-208
- NVD API JSON record for CVE-2026-126156
- Fortinet: Security Hardening Release for Multiple Products
- FortiMail 8.0.2 Release Notes: Introduction and Supported Models
- FortiMail 8.0.2 Release Notes: Resolved Issues
- FortiMail 8.0.2 Release Notes (PDF)
- Briefing: Fortinet hardening updates, details withheld until 10 November
- FortiMail 8.0.2 Administration Guide: Configuring IBE Encryption
- FortiMail Identity Based Encryption White Paper
- MITRE CWE-639: Authorization Bypass Through User Controlled Key
- CISA: Adds One Known Exploited Vulnerability to Catalog (1 October 2026)
- CISA: Fortinet Advisory on New Post Exploitation Technique (April 2025)
- CISA: Fortinet Releases Security Updates for FortiOS (December 2022)
- HKCERT: Fortinet Products Multiple Vulnerabilities
- Fortinet's Commitment to Product Security and Integrity (PDF)
- Fortinet: About Us
- Fortinet: Leader in the 2025 Gartner Magic Quadrant for SASE Platforms
- StackFlag: CVE-2026-126156 FortiMail
- Rescana: Fortinet November 2026 PSIRT coverage



