Automated Threat Modeling

Brief Summary: FortiMail CVE-2026-126150, Unauthenticated IBE Webmail Password Reset Leading to Account Takeover

A brief summary of CVE-2026-126150, a critical (CVSS 9.1) weak password recovery flaw in Fortinet FortiMail that may let an unauthenticated attacker reset any IBE webmail user's password. Covers affected branches, the fixed builds from FG-IR-26-202, and why upgrading past the minimum build is advisable.

CVE Analysis

8 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Brief Summary: FortiMail CVE-2026-126150, Unauthenticated IBE Webmail Password Reset Leading to Account Takeover

Introduction

Fortinet has disclosed a critical flaw in FortiMail that may let an unauthenticated attacker reset the password of any Identity Based Encryption (IBE) webmail user and take over that account using specially crafted HTTP requests. For organizations that use FortiMail IBE to deliver secured messages to recipients, the issue lands directly on the access boundary that is supposed to keep those messages limited to their intended reader.

Fortinet is a cybersecurity and networking vendor headquartered in Sunnyvale, California, with a portfolio of more than 50 enterprise products and recognition as a Leader in the 2025 Gartner Magic Quadrant for SASE Platforms. FortiMail is its email product, and one of its features is IBE: recipients of secured mail receive a notification, register or authenticate on the FortiMail unit, and then read the protected message through IBE webmail. IBE exists to protect sensitive correspondence, so a weakness in how IBE webmail accounts are recovered affects exactly the data organizations chose to encrypt.

The issue is tracked as CVE-2026-126150. Fortinet published advisory FG-IR-26-202 on November 10, 2026, and NVD published the record on November 11, 2026. The NVD data lists the vendor as Unknown, but the record was filed by [email protected] and the affected product is Fortinet FortiMail. Fortinet, as CNA, assigns a CVSS v3.1 base score of 9.1 (Critical). NVD has not supplied its own assessment.

Technical Information

Severity and vector

The published base vector is:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

In plain terms: network reachable, low attack complexity, no privileges required, no user interaction, high confidentiality and integrity impact, and no scored availability impact. Fortinet's expanded vector also includes E:U, which FIRST defines as Unproven exploit maturity (no available exploit code, or a theoretical exploit). As FIRST notes, a CVSS score describes technical severity. It is not a measure of organizational risk or evidence of active attacks.

Root cause: reading the two CWE labels together

The two Fortinet-authored classifications disagree on the label but describe the same defect from different angles:

  • CWE-640, Weak Password Recovery Mechanism for Forgotten Password (NVD record). MITRE describes this as a recovery or change mechanism that works without the original password but is weak enough to permit unauthorized account access. A weak recovery path can undermine otherwise strong password authentication.
  • CWE-306, Missing Authentication for Critical Function (advisory summary). This frames the password reset action itself as a critical function reachable without authentication.

Combined, the picture is an IBE webmail password reset action that an unauthenticated requester can reach with crafted HTTP requests and use to reset any IBE user's password, with nothing proving that the requester owns the account. The sources do not reconcile the two labels, and Fortinet has not published which internal check fails.

What follows is our inference from the CWE labels, not a confirmed description of Fortinet's patch. A fix for this class of bug has to make the reset step require proof bound to the specific account, such as a single-use, unguessable token or an answer to a secret challenge, validated on the server and tied to that one recipient. A request that merely names the target account should no longer be sufficient. MITRE's general CWE-640 guidance points the same way. It recommends thorough validation of recovery input and preventing the requester from controlling where a replacement password is sent.

The IBE access boundary

Fortinet's administration guide describes IBE users as recipients who receive secured mail notifications and register or authenticate on the FortiMail unit. Access to the secure message follows the relevant registration and token verification steps. CVE-2026-126150 breaks the account layer protecting that workflow.

The published description supports IBE webmail account takeover. It does not establish administrator takeover, operating system compromise or remote code execution, and those outcomes should not be read into this CVE.

Attack flow

Based on the vendor and NVD descriptions, the documented sequence is:

  1. An attacker with network access to an affected FortiMail unit targets the IBE webmail password recovery functionality. No existing session is needed.
  2. The attacker sends specially crafted HTTP requests that identify an arbitrary IBE webmail user as the target. The original password is not required, and the victim does not need to take any action.
  3. On an affected build, the password of the targeted IBE user is reset without proof that the requester controls the account.
  4. The attacker uses the account under the new credentials, taking over that user's IBE webmail access and the secured messages it exposes.

The public disclosures do not include the vulnerable HTTP route, request parameters, reset token behavior, a concrete request sequence or exploit code, so the precise implementation defect remains unspecified.

Exploitation status

FG-IR-26-202 lists Known Exploited: No. We found no named threat actor, public exploit or confirmed campaign for this CVE in the reviewed material. The examined CISA KEV feed did not include it, but that snapshot is dated November 10, 2026, one day before NVD publication, so its absence says nothing about status after disclosure. This is the current evidence, and it does not rule out attacks.

Patch Information

FortiMail is closed-source firmware, and no public code diff exists for this fix. Fortinet ships fixes as new firmware builds, and the source of truth is advisory FG-IR-26-202, the only reference NVD lists for this CVE.

Fixed releases from FG-IR-26-202

  • FortiMail 8.0: vulnerable 8.0.0. First fixed build: 8.0.1.
  • FortiMail 7.6: vulnerable 7.6.0 through 7.6.5. First fixed build: 7.6.6.
  • FortiMail 7.4: vulnerable 7.4.0 through 7.4.7. First fixed build: 7.4.8.
  • FortiMail 7.2: vulnerable 7.2.0 through 7.2.9. The fix, 7.2.10, is described as upcoming and not yet released, with no release date stated.
  • FortiMail Cloud: fixed by Fortinet on October 5, 2026. Customers do not need to do anything for this issue.

Fortinet marks Virtual Patch: No, meaning no FortiGuard IPS or WAF signature covers this bug, and the advisory provides no workaround. Upgrading firmware is the only fix the vendor offers. A third-party patch tracker that reviewed the November advisories confirms FG-IR-26-202 still points 7.2 users to an upcoming 7.2.10. A secondary vulnerability summary suggests disabling password recovery, but it gives no Fortinet configuration procedure and is not a vendor-documented workaround.

The fixed builds do not name this CVE

The FortiMail 7.6.6 release notes (build 852, published September 22, 2026) contain a Common Vulnerabilities and Exposures table listing four CWE references: CWE-89, CWE-22, CWE-1050 and CWE-472. None of them is CWE-306 or CWE-640.

The CWE-472 entry (bug 1286744) is the only one that looks related to parameter tampering. However, the 8.0.0 release notes list that same bug as fixed, while the advisory says 8.0.0 is still vulnerable to CVE-2026-126150, so bug 1286744 is not this fix. Fortinet has not publicly linked CVE-2026-126150 to any bug ID, which means you cannot confirm the fix by reading release notes. Rely on the advisory's version table.

Timing

The 7.6.6 fix was available roughly seven weeks before the CVE was disclosed. That fits Fortinet's October 2026 hardening release approach, where fixes ship first and CVEs are published later. Anyone comparing firmware builds side by side could have identified the change before the advisory appeared.

Upgrade past the minimum build

The versions in FG-IR-26-202 are the minimum builds for this single CVE. According to the patch tracker's summary of the November advisories, the other FortiMail critical issues disclosed the same day affect 8.0.0 through 8.0.1, 7.6.0 through 7.6.6 and 7.4.0 through 7.4.8, and are fixed in 8.0.2, 7.6.7 and 7.4.9. Several of those are also IBE webmail account takeover bugs (FG-IR-26-207, FG-IR-26-208 and FG-IR-26-209), and the tracker reports that most of those advisories tell 7.2 users to move to the 7.4 branch.

In practice, a host on 7.6.6 or 7.4.8 is fixed for CVE-2026-126150 but remains exposed to related IBE takeover bugs. Our recommendation, grounded in that advisory set:

  • 8.0 deployments: plan for 8.0.2
  • 7.6 deployments: plan for 7.6.7
  • 7.4 deployments: plan for 7.4.9
  • 7.2 deployments: move to a fixed 7.4 or later build instead of waiting for 7.2.10

For teams validating their own remediation, the expectation on a patched build is that the same crafted reset requests fail.

Affected Systems and Versions

  • FortiMail 8.0.0
  • FortiMail 7.6.0 through 7.6.5
  • FortiMail 7.4.0 through 7.4.7
  • FortiMail 7.2.0 through 7.2.9

The vulnerable component is the IBE webmail password recovery functionality, and the affected accounts are IBE webmail users. FortiMail Cloud was remediated by Fortinet on October 5, 2026 and requires no customer action for this issue. The cloud statement does not replace the upgrade guidance for customer-managed deployments.

Vendor Security History

This issue was discovered and reported internally by Gwendal Guegniaud of the Fortinet Product Security team. Fortinet's response includes explicit affected ranges, branch-specific upgrade targets and a separate cloud remediation statement, with the cloud service fixed about five weeks before the public advisory.

FortiMail has recent confirmed exploitation history through a different bug. On October 1, 2026, CISA added CVE-2026-104286, a FortiMail path traversal vulnerability, to its Known Exploited Vulnerabilities catalog based on evidence of active exploitation. That confirmation applies to CVE-2026-104286 only. Fortinet lists Known Exploited: No for CVE-2026-126150.

Across the broader Fortinet portfolio, CISA in April 2025 described a malicious file placed on FortiGate devices through exploitation of separate vulnerabilities, potentially exposing filesystem files including configurations. That case concerns FortiGate and FortiOS, not this FortiMail password recovery flaw, and its attacker behavior should not be transferred to this CVE.

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