Introduction
Fortinet has disclosed a missing authentication flaw in FortiMail that may let an unauthenticated attacker reach other users' secure email accounts using nothing more than crafted HTTP requests. FortiMail's secure mail features exist to protect sensitive messages, so a gap in the API layer that guards those mailboxes undercuts one of the main reasons organizations deploy them.
The issue is tracked as CVE-2026-126157, carries a CVSS 3.1 base score of 9.1 (Critical), and is addressed in Fortinet PSIRT advisory FG-IR-26-209, published November 10, 2026. NVD published its record on November 11, 2026. Fortinet reports no known exploitation, and the issue was found internally. This post is a brief summary of what the vendor and NVD records establish, what they leave open, and how the fixed releases map to each FortiMail branch.
Technical Information
Root cause
Fortinet identifies the affected component as the FortiMail API. The advisory describes a missing authentication vulnerability: functionality that should require a proven identity is reachable without one. Fortinet categorizes the resulting impact as improper access control, and the practical outcome is access to other users' secure email accounts.
The two public records use related CWE labels:
- NVD: CWE-287, Improper Authentication. MITRE defines this as a failure to prove, or sufficiently prove, that an actor's claimed identity is correct.
- Fortinet advisory: CWE-306, Missing Authentication for Critical Functionality. MITRE defines this as functionality requiring a provable identity, or consuming significant resources, being available without authentication, and explicitly places it beneath CWE-287.
CWE-287 is the broad category and CWE-306 is its more specific child, so the two labels describe one bug. Read together, they point to an HTTP-reachable function in the secure mail (webmail or encrypted mailbox) part of FortiMail that served or changed a user's mailbox without first checking who was making the request. The fixed builds would be expected to add the missing authentication check, plus a check that the session actually belongs to the mailbox being accessed, before that function runs. Fortinet has not published which endpoint or handler changed, so treat this as an inference from the CWE classification rather than confirmed implementation detail.
Why secure mail authentication matters here
Fortinet's FortiMail documentation describes an identity-based encryption (IBE) workflow in which recipients access protected messages through notification links and registration, and identities such as email addresses contribute to key calculation. Account authentication is therefore central to how protected mail reaches recipients. The advisory does not say which step of that workflow fails, and nothing published indicates the flaw involves the cryptography itself.
CVSS breakdown
The published base vector is:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- Attack vector: Network.
- Attack complexity: Low.
- Privileges required: None. Authentication is not a meaningful prerequisite.
- User interaction: None.
- Scope: Unchanged.
- Confidentiality: High, Integrity: High. Consistent with reading and altering mailbox content.
- Availability: None.
NVD attributes the score to Fortinet as the source. NVD has not yet provided its own assessment, and the API record is in "Received" status. The score describes assessed exploitation conditions and consequences. It is not evidence that attacks have occurred.
Attack flow
Based only on what the advisory and CVSS record state, exploitation looks like this:
- The attacker has network reach to the HTTP interface of a FortiMail instance running an affected release.
- No credentials or victim interaction are needed (PR:N, UI:N).
- The attacker sends crafted HTTP requests to the affected API functionality, which processes them without authenticating the requester.
- The attacker gains access to another user's secure email account. The CVSS assessment rates the confidentiality and integrity impact as high and the availability impact as none.
The advisory does not disclose the vulnerable endpoint, HTTP method, request parameters, payload, token handling, request sequence, or any configuration prerequisite beyond the affected product and versions. A more detailed exploit chain cannot be established from public material, and the available evidence does not support describing this as remote code execution, cryptographic key recovery, an SMTP exploit, or full appliance takeover.
Exploitation status
Fortinet's advisory reports "Known Exploited: No." The issue was discovered internally and is credited to Gwendal Guegniaud of the Fortinet Product Security team, using the AI model Claude Mythos. That credit acknowledges a researcher and says nothing about threat actors. No campaign, actor, victim, malware family, payload or indicators of compromise have been published for this CVE, and we found no verified public proof of concept. This is a critical technical exposure with no exploitation known to Fortinet, and the lack of known exploitation does not change the requirement to upgrade.
Patch Information
Fortinet fixed this in new firmware releases described in FG-IR-26-209. FortiMail is closed source, so there is no public commit, diff or source-level changelog. The firmware versions in the advisory are the only patch evidence that can be checked.
Fixed releases by branch
- FortiMail 8.0: 8.0.0 through 8.0.1 are vulnerable. Upgrade to 8.0.2 or above.
- FortiMail 7.6: 7.6.0 through 7.6.6 are vulnerable. Upgrade to 7.6.7 or above.
- FortiMail 7.4: 7.4.0 through 7.4.8 are vulnerable. Upgrade to 7.4.9 or above.
- FortiMail 7.2: all versions are vulnerable. There is no fix on this branch, so migrate to a fixed release.
- FortiMail 7.0: all versions are vulnerable. There is no fix on this branch, so migrate to a fixed release.
Only the 8.0, 7.6 and 7.4 branches receive a fix. Devices on 7.2 or 7.0 get no backport and must move to a supported branch (7.4.9+, 7.6.7+ or 8.0.2+) to be protected, so plan for a major version upgrade on those systems rather than a quick maintenance update.
FortiMail Cloud
Fortinet fixed the hosted service on its own side on October 5, 2026, more than a month before the advisory was published, moving all Cloud firmware to 7.6.7 GA or 8.0.2 GA. The advisory says FortiMail Cloud customers do not need to take action. This also indicates that 7.6.7 and 8.0.2 are the first builds containing the fix. The no-action statement applies only to the named managed service. It does not cover customer-operated FortiMail virtual machines or installations you host yourself in a cloud environment.
Notes on the fix
- The advisory marks Virtual Patch as "No", so no FortiGuard IPS or WAF signature is offered as a stopgap, and no MFA setting, password reset or feature disablement is documented as a workaround. Upgrading the firmware is the only fix.
- The 8.0.2 and 7.6.7 release notes instruct administrators to back up the configuration and other stored data before upgrading or downgrading, and to follow the documented firmware upgrade paths when moving between branches. After the upgrade, clear the browser cache before logging in to the web interface so screens render correctly. The 8.0.2 notes state that downgrading is generally not recommended or supported and direct customers to Fortinet Technical Support before attempting it.
- Internal discovery explains why Cloud was quietly remediated before public disclosure.
- At least one upstream feed returned BusyBox and Yocto patches for CVE-2026-26157. That is a different CVE with no relation to this FortiMail fix.
Affected Systems and Versions
- FortiMail 8.0.0 through 8.0.1
- FortiMail 7.6.0 through 7.6.6
- FortiMail 7.4.0 through 7.4.8
- FortiMail 7.2, all versions (NVD's CNA-supplied version data lists the end of the unpatched range as 7.2.9)
- FortiMail 7.0, all versions (NVD's CNA-supplied version data lists the end of the unpatched range as 7.0.9)
NVD's free-text description omits the 7.0 branch, but both the Fortinet advisory and NVD's structured affected product data include it. Do not rely on the short description alone when scoping. FortiMail Cloud was affected but has already been remediated by Fortinet. The advisory does not identify any configuration requirement beyond running an affected release.
Vendor Security History
Fortinet's PSIRT policy describes a defined process for receiving, investigating and publicly reporting vulnerabilities, prioritizing remediation using CVSS and other factors, and publishing advisories on the second Tuesday of each month, with additional advisories possible for critical issues. For this CVE, the visible outputs of that process are internal discovery, branch-specific fixed releases, an early Cloud repair, and a public advisory.
Fortinet's track record also includes consequential exploitation in a different product. On October 24, 2024, Mandiant reported investigating, with Fortinet, mass exploitation of CVE-2024-47575 in FortiManager involving 50+ potentially compromised devices. That flaw allowed an attacker operating an unauthorized FortiManager device to execute code or commands against vulnerable FortiManager systems. Mandiant observed the cluster UNC5820 exploiting it as early as June 27, 2024, staging and exfiltrating managed FortiGate configuration data including appliance details, users and hashed passwords. Mandiant reported no evidence at that stage of further lateral compromise using the data. CISA also published updated guidance and indicators for that incident.
That case is useful vendor context, but it is a separate vulnerability in a separate product, and nothing links UNC5820 to CVE-2026-126157.
References
- NVD: CVE-2026-126157
- CVE Record: CVE-2026-126157
- Fortinet PSIRT Advisory FG-IR-26-209
- NVD API record for CVE-2026-126157
- MITRE CWE-287: Improper Authentication
- MITRE CWE-306: Missing Authentication for Critical Functionality
- FortiMail 8.0.2 Release Notes
- FortiMail 7.6.7 Release Notes
- FortiMail 8.0.2 Administration Guide: Configuring IBE encryption
- Fortinet Security Vulnerability Policy
- HKCERT: Fortinet Products Multiple Vulnerabilities
- StackFlag: CVE-2026-126157 in FortiMail
- VulDB: CVE-2026-126157
- Mandiant / Google Cloud: Investigating FortiManager Zero Day Exploitation (CVE-2024-47575)
- CISA: Fortinet Updates Guidance and Indicators of Compromise following FortiManager Vulnerability Exploitation



