Automated Threat Modeling

Overview of CVE-2026-126155: FortiMail IBE Webmail Incorrect Authorization Allows Recipient Session Takeover

A brief summary of CVE-2026-126155, an incorrect authorization flaw in Fortinet FortiMail IBE webmail that may let an unauthenticated remote attacker obtain a session as any IBE recipient and read or send their encrypted mail. Covers affected versions, fixed releases, and advisory metadata inconsistencies.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Overview of CVE-2026-126155: FortiMail IBE Webmail Incorrect Authorization Allows Recipient Session Takeover

Introduction

FortiMail's Identity Based Encryption (IBE) webmail exists so that sensitive mail sent to external recipients can only be opened by the person it was addressed to. CVE-2026-126155 breaks that guarantee at the access control layer. Fortinet says an unauthenticated remote attacker may use crafted HTTP requests to obtain an authenticated IBE webmail session as any IBE recipient, then read or send that recipient's encrypted mail.

FortiMail is Fortinet's email security product, sold as hardware appliances, virtual machines, and the vendor-managed FortiMail Cloud service. Fortinet scores this issue CVSS 3.1 9.1 (Critical), published it in advisory FG-IR-26-207 on November 10, 2026, and credits internal discovery to Gwendal Guegniaud of its Product Security team, who used the AI model Claude Mythos. The advisory lists the issue as not known to be exploited. Fixed firmware is available for the 8.0, 7.6, and 7.4 branches, while 7.2 deployments must migrate.

Technical information

Root cause: an authorization check that reaches the wrong answer

Fortinet identifies the affected component as API and classifies the weakness as CWE-863, Incorrect Authorization. MITRE defines CWE-863 as a case where the product performs an authorization check when an actor attempts to access a resource or perform an action, but the check is performed incorrectly. That differs from CWE-862 (Missing Authorization). An access decision exists in the IBE webmail flow, but it can be steered to grant a session to the wrong party.

Fortinet has not published the vulnerable endpoint, HTTP method, parameters, session token handling, or the specific faulty condition. FortiMail is closed source, so there is no public diff or code to review. The advisory is precise only about the outcome. The flawed decision yields an authenticated IBE webmail session bound to an arbitrary recipient, for a requester who has never authenticated as that recipient.

Why the impact follows from how IBE works

Fortinet documents IBE as public key encryption that uses an identity, such as an email address, to derive encryption keys. In normal operation:

  • The recipient receives a notification containing an HTML attachment with access instructions and links.
  • A first-time recipient registers before reading the message.
  • Once the recipient is authenticated, FortiMail decrypts the message automatically when it is opened.

Because decryption is performed on behalf of whoever holds a valid recipient session, the encryption itself never needs to be defeated. If an attacker can obtain that session, FortiMail does the decryption for them. Our reading of the sources is that this is an access control failure in front of the encrypted mailbox, not a weakness in the underlying cryptography.

Attack flow

Based solely on the advisory description, the attack proceeds as follows:

  1. The attacker reaches the FortiMail IBE webmail interface over the network. No credentials and no victim interaction are required.
  2. The attacker sends crafted HTTP requests to the affected API component, targeting an IBE recipient identity of their choosing.
  3. The incorrect authorization decision results in an authenticated IBE webmail session as that recipient.
  4. Using that session, the attacker can read the recipient's encrypted mail, and can send encrypted mail as the recipient.

Step 4 accounts for both the confidentiality and integrity ratings. Reading exposes protected content, and sending lets the attacker impersonate the recipient inside a channel that recipients and senders treat as trusted.

CVSS 3.1 breakdown

The vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, supplied by Fortinet as the CNA. NVD has not published its own assessment.

  • Attack Vector: Network, reachable remotely.
  • Attack Complexity: Low in the published scoring.
  • Privileges Required: None.
  • User Interaction: None.
  • Scope: Unchanged.
  • Confidentiality: High, encrypted mail can be read.
  • Integrity: High, mail can be sent as the recipient.
  • Availability: None.

Metadata inconsistencies worth knowing about

Two discrepancies appear in the published records:

  • The advisory Impact field and, per Rescana, the CSAF threat entry for FG-IR-26-207 both say "Denial of service." The written summary, the CVE description, and the CVSS vector (A:N) all describe session takeover with read and send access. The summary and vector are the consistent pair.
  • NVD's affected product configuration enumerates 7.2.0 through 7.2.9, while the CVE description and Fortinet's advisory say all 7.2 versions are affected. Fortinet's broader statement should drive remediation.

Dates also differ by record. Fortinet published the advisory on November 10, 2026, and NVD received and recorded the CVE on November 11, 2026.

Patch information

Fortinet fixed CVE-2026-126155 in firmware releases on every supported FortiMail branch except 7.2, as described in advisory FG-IR-26-207. There is no public commit, diff, or code snippet. Everything below comes from the vendor advisory and its fixed version table.

What the fix has to do

Since the flaw is CWE-863 in the IBE session logic, the fixed builds need to bind a webmail session to the recipient who actually proved their identity and refuse requests that try to claim a different identity. Fortinet has not said which handler or parameter changed.

Fixed releases

  • FortiMail 8.0: affected 8.0.0 through 8.0.1; fixed in 8.0.2 or later.
  • FortiMail 7.6: affected 7.6.0 through 7.6.6; fixed in 7.6.7 or later.
  • FortiMail 7.4: affected 7.4.0 through 7.4.8; fixed in 7.4.9 or later.
  • FortiMail 7.2: all versions affected (NVD lists 7.2.0 through 7.2.9); no fix. Migrate to one of the fixed branches above.

Key points

  • Fortinet's instruction for 7.2 is to "migrate to a fixed release," so the only remedy there is a branch upgrade to 7.4.9, 7.6.7, or 8.0.2 or later, planned through Fortinet's supported upgrade path. There is no backport.
  • Fortinet moved all FortiMail Cloud firmware to 7.6.7 GA or 8.0.2 GA on October 5, 2026, more than a month before the advisory. Cloud customers need not act. The timing also means 7.6.7 and 8.0.2 carried the fix well before the public notice, so customer-managed appliances below those builds remained exposed to a bug already fixed elsewhere.
  • The advisory states "Virtual Patch: No." No IPS signature has been published to block exploit traffic while an upgrade is pending, so new firmware is the only vendor fix.
  • According to Rescana's review of the advisory pages and CSAF files, the same FortiMail versions also fix the related IBE takeover bug FG-IR-26-208 (CVE-2026-126156, CWE-639), FG-IR-26-199 (path traversal), and FG-IR-26-216 (SQL injection). One upgrade covers all of them.

A labeling inconsistency to watch for

If your patch prioritization tooling consumes the CSAF Impact field, it will see "Denial of service" and may rank this fix too low. The CVSS 3.1 score of 9.1 with C:H/I:H/A:N matches the takeover description. Use the summary and vector when ranking.

Credit

The issue was found internally by Gwendal Guegniaud of the Fortinet Product Security team using the frontier AI model Claude Mythos. No outside researcher was involved, and no write-up was published before the 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 configuration table enumerates 7.2.0 through 7.2.9)
  • FortiMail Cloud: affected prior to Fortinet's October 5, 2026 update; now remediated by the vendor.

The disclosed impact concerns IBE recipients and IBE webmail sessions. The advisory does not describe any configuration that removes exposure on an affected version, and Fortinet's general IBE authentication settings are not documented as a mitigation for this defect.

Vendor security history

  • On October 1, 2026, CISA added the separate FortiMail path traversal vulnerability CVE-2026-104286 to its Known Exploited Vulnerabilities Catalog based on evidence of active exploitation. This shows FortiMail is an attacker target, but it is not evidence that CVE-2026-126155 has been exploited.
  • Fortinet's advisory FG-IR-26-202 for CVE-2026-126150, a password reset and account takeover issue, lists 8.0.1, 7.6.6, and 7.4.8 as fixed releases. Each of those versions is still affected by CVE-2026-126155, so a deployment patched for that advisory is not patched for this one. Describing a system as "patched FortiMail" is not precise enough without naming the advisory.
  • Fortinet reports that approximately 60% of vulnerabilities discovered in 2025 were identified internally, and describes practices including static and dynamic testing, software composition analysis, fuzzing, AI-assisted code auditing, and penetration testing. Its disclosure policy publishes advisories monthly, with out-of-cycle releases for critical issues or observed exploitation.
  • Fortinet reports that Gartner named it a Challenger in the 2025 Magic Quadrant for Email Security (report dated December 1, 2025).

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