CVE
A incorrect authorization vulnerability in Fortinet FortiMail 8.0.0 through 8.0.1, FortiMail 7.6.0 through 7.6.6, FortiMail 7.4.0 through…
Affects Fortinet FortiMail 8.0.0-8.0.1, 7.6.0-7.6.6, 7.4.0-7.4.8 and all 7.2 versions. Fixed in 8.0.2, 7.6.7 and 7.4.9.
Written by anthropic/claude-sonnet-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.0.2, 7.6.7, 7.4.9
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 8.0.2, 7.6.7, 7.4.9.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 40/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Fortinet FortiMail has an incorrect authorization flaw that lets an attacker take over an authenticated IBE webmail session as any IBE recipient, then read or send that person's encrypted mail. The attacker can do this remotely, without logging in, by sending crafted HTTP requests.
Read the original description
A incorrect authorization vulnerability in Fortinet 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 may allow an unauthenticated remote attacker to obtain an authenticated IBE webmail session as any IBE recipient and read or send their encrypted mail via crafted HTTP requests.
Who should check
Teams running self-managed Fortinet FortiMail 7.2, 7.4, 7.6 or 8.0 (pre-fix versions) that offer IBE webmail for encrypted mail. FortiMail Cloud is already remediated.
Read the source excerpt
“FortiMail 7.6 7.6.0 through 7.6.6 Upgrade to 7.6.7 or above”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach14/20Affects Fortinet (an enterprise product or network appliance)
- Severity9.1/10CVSS 9.1
- No patch0/5No signal
What would change the score
- Would score about 85 if added to CISA KEV
- Would score about 80 if CISA's SSVC rates exploitation active
- Would score about 45 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 8.0.2, 7.6.7, 7.4.9.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126155 (A incorrect authorization vulnerability in Fortinet FortiMail 8.0.0 through 8.0.1, FortiMail 7.6.0 through 7.6.6, FortiMail 7.4.0 through…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126155 (entry last updated 2026-11-11):
Affected:
- Fortinet FortiMail: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.6; from 7.4.0, through 7.4.8; from 7.2.0, through 7.2.9
Fixed versions: 8.0.2, 7.6.7, 7.4.9.
Conditions (all must be true for the bug to be hit):
- FortiMail 8.0.0 through 8.0.1 (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-207)
- FortiMail 7.6.0 through 7.6.6 (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-207)
- FortiMail 7.4.0 through 7.4.8 (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-207)
- FortiMail 7.2, all versions (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-207)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126155 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126155 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://fortiguard.fortinet.com/psirt/FG-IR-26-207
- https://www.cve.org/CVERecord?id=CVE-2026-126155
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126155
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126155"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Fortinet FortiMail
From 8.0.0 · through 8.0.1; From 7.6.0 · through 7.6.6; From 7.4.0 · through 7.4.8; From 7.2.0 · through 7.2.9
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126155
Is CVE-2026-126155 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An incorrect authorization flaw lets an unauthenticated remote attacker send crafted HTTP requests to get an authenticated IBE webmail session as any IBE recipient. That session allows reading or sending the recipient's encrypted mail.Source: fortiguard.fortinet.com, cve.org
Which versions are affected by CVE-2026-126155?
FortiMail: from 8.0.0 through 8.0.1; from 7.6.0 through 7.6.6; from 7.4.0 through 7.4.8; from 7.2.0 through 7.2.9.Source: cve.now feed data
Am I affected, and how do I check?
Affected are FortiMail 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, 7.4.0 through 7.4.8, and all 7.2 versions. The installed FortiMail version can be checked in the appliance's firmware or system information and compared against these ranges.Source: fortiguard.fortinet.com, cve.org
How do I fix CVE-2026-126155?
Upgrade to FortiMail 8.0.2 or above, 7.6.7 or above, or 7.4.9 or above. The facts list no workaround and name no fixed 7.2 release, so 7.2 users would need to move to one of the fixed branches.Source: fortiguard.fortinet.com, cve.org