Fortinet says an unauthenticated remote party may take over an IBE recipient account.Fortinet rates it Critical at 9.1 on CVSS 3.1. The vendor published advisory FG-IR-26-208 on November 10, 2026.
What it allows
What Can CVE-2026-126156 Affect?
Fortinet classifies the flaw as authorization bypass (CWE-639). NVD records the same weakness identifier.
This flaw can give an outsider control of an IBE recipient account. Track it separately from the IBE password reset flaw.
The advisory lists the FortiMail API. Start with hosts that let outside users reach IBE webmail. Verify each host’s release before you assign a fix.
Fortinet marked Known Exploited as No at publication. CVE-2026-126156 was absent from CISA KEV catalog version 2026.11.10.
Compare the Fortinet November critical advisory roundup for other product fixes. The earlier FortiMail file-write advisory describes a separate issue.
Who is affected
Which Releases Does CVE-2026-126156 Affect?
Fortinet lists 4 affected FortiMail release lines in FG-IR-26-208. Match your installed branch to the solution in the table.
| FortiMail line | Affected releases | Fortinet solution |
|---|---|---|
| FortiMail 8.0 | 8.0.0 through 8.0.1 | Upgrade to 8.0.2 or above |
| FortiMail 7.6 | 7.6.0 through 7.6.6 | Upgrade to 7.6.7 or above |
| FortiMail 7.4 | 7.4.0 through 7.4.8 | Upgrade to 7.4.9 or above |
| FortiMail 7.2 | 7.2 all versions | Migrate to a fixed release |
Fortinet directs teams on 7.2 to migrate to a fixed release. Use the vendor’s supported upgrade path and verify the installed release after maintenance.
Fortinet says it remediated the issue in FortiMail Cloud on October 5, 2026. The vendor says its Cloud customers need take no action for this CVE.
Fortinet lists no virtual patch. The vulnerability management guide explains how to verify remediation across an inventory.
Timeline
- 2026-10-05
Fortinet says it remediated the issue in FortiMail Cloud.
- 2026-11-10
Fortinet published FG-IR-26-208 and marked Known Exploited as No.
- 2026-11-11
NVD published its record for CVE-2026-126156.
What to do
-
Inventory affected FortiMail deployments
Record each installed branch and whether FortiMail is self-managed or hosted in FortiMail Cloud. Use the vendor table to identify deployments that need action.
-
Follow the release-line fix
Use 8.0.2, 7.6.7 or 7.4.9 or later for the corresponding release line. Follow the migration instructions for affected branches without an in-branch fix.
-
Review relevant account activity
Review IBE recipient account activity and reports of unauthorized account changes. Investigate suspected account misuse and follow your incident response process.
-
Verify the upgrade
Confirm the running release after the change. Recheck FG-IR-26-208 for any later changes to the affected range or remediation guidance.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-126156 in Brandefense Atlas
The Atlas record of CVE-2026-126156: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What is CVE-2026-126156?
It is a FortiMail recipient account takeover flaw. Fortinet says an unauthenticated remote party may take over an IBE recipient account.
Which accounts does the advisory describe?
The advisory’s account impact refers to IBE recipient accounts.
Do FortiMail Cloud customers need to act?
Fortinet says it remediated this issue in FortiMail Cloud on October 5, 2026. The vendor says those customers need take no action.
What does Fortinet say about exploitation?
Fortinet marked Known Exploited as No at publication. The CVE was absent from CISA KEV catalog version 2026.11.10.
Sources
- Fortinet advisory FG-IR-26-208Fortinet PSIRT
- CVE-2026-126156National Vulnerability Database
- Known Exploited Vulnerabilities CatalogCISA