Fortinet says an unauthenticated party may gain access to another user’s secure email account.Fortinet rates it Critical at 9.1 on CVSS 3.1. The vendor published advisory FG-IR-26-209 on November 10, 2026.
What it allows
What Can CVE-2026-126157 Affect?
Fortinet classifies the flaw as missing authentication for a critical function (CWE-306). NVD records CWE-287 for the same CVE.
Fortinet’s impact statement concerns access to other users’ secure email accounts. Its version table also covers the entire FortiMail 7.0 branch.
The advisory identifies the FortiMail API component and rates the issue Critical. Review IBE webmail reachability and prioritize the affected installations that are accessible to untrusted users.
Fortinet marked Known Exploited as No at publication. CVE-2026-126157 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-126157 Affect?
Fortinet lists 5 affected FortiMail release lines in FG-IR-26-209. 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 |
| FortiMail 7.0 | 7.0 all versions | Migrate to a fixed release |
Fortinet directs teams on 7.0 and 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-209 and marked Known Exploited as No.
- 2026-11-11
NVD published its record for CVE-2026-126157.
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 secure email account access for activity that differs from expected use. Escalate unexplained access and assess whether protected messages may be affected.
-
Verify the upgrade
Confirm the running release after the change. Recheck FG-IR-26-209 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-126157 in Brandefense Atlas
The Atlas record of CVE-2026-126157: 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-126157?
It is a FortiMail secure email access flaw. Fortinet says an unauthenticated party may gain access to another user’s secure email account.
What should FortiMail 7.0 and 7.2 users do?
Fortinet lists all versions in both release lines as affected. The advisory directs customers on either line to migrate to a fixed release.
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-209Fortinet PSIRT
- CVE-2026-126157National Vulnerability Database
- Known Exploited Vulnerabilities CatalogCISA