Improper authorization in Fortinet FortiManager enables unauthenticated code or command execution

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-126261?

CVE-2026-126261 is a vulnerability classified as Improper Authorization, affecting FortiManager (affected versions: 8.0.0, 7.6.0 – ≤ 7.6.7, and other affected versions). This vulnerability is rated Critical, with a CVSS score of 9. There is not enough data to determine whether this vulnerability has been exploited.

Overview

Original source data

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.

Affected products and scope

  • FortiManager 8.0: version 8.0.0 is affected. The supplied solution identifies 8.0.1 or above as the upgrade target.
  • FortiManager 7.6: versions 7.6.0 through 7.6.7 are affected. The supplied solution identifies 7.6.8 or above as the upgrade target.
  • FortiManager 7.4: versions 7.4.0 through 7.4.5 are affected. The supplied solution identifies 7.4.6 or above as the upgrade target.
  • FortiManager 7.2: versions 7.2.0 through 7.2.8 are affected. The supplied solution identifies 7.2.9 or above as the upgrade target.

The record sets the product's default status to unaffected outside the ranges listed above, but the available evidence does not independently validate every later or parallel release branch.

Technical details

The flaw is an authorization failure in FortiManager's handling of FGFM packets. The attacker-controlled input is a crafted FGFM packet delivered to the FGFM port. The attacker does not need to authenticate, but must have network reachability to that port; the supplied assessment also indicates low attack complexity and no user interaction. If the packet is accepted through the vulnerable path, the documented outcome is execution of code or commands. The available evidence does not identify the exact authorization check, packet fields, internal module, or execution privilege context, so those details should not be inferred. Exposure is limited to the listed FortiManager releases and deployments where the FGFM port is reachable by the attacker.

Exploitability

The vulnerability is remotely reachable over the network when the FGFM port is accessible from the attacker's position. The supplied information indicates that the attacker needs no account or prior privileges and that no user interaction is required. Attack complexity is assessed as low. The record does not establish active exploitation or the availability of a public exploit, and the authoritative content inspected does not establish either status. Reachability of the FGFM port remains the key precondition.

Technical impact

The documented technical outcome is execution of code or commands through crafted FGFM packets. This could affect the confidentiality, integrity, and availability of FortiManager. Because authentication and user interaction are not required, exploitation could occur before the attacker has an account in the product. The supplied assessment describes unchanged scope, but the exact privileges of the executed code or commands and any ability to affect other systems are not established. Real-world consequences depend on process privileges, deployment configuration, and the functions exposed by FortiManager.

Business impact

If exploited, the vulnerability could allow code or command execution on FortiManager without credentials. Depending on the privileges of the process and the executed command, an attacker could affect the confidentiality, integrity, or availability of the management system. This could disrupt administrative operations or cause configuration changes, but the available evidence does not identify a specific intrusion scenario, victim, or breach. The exact execution privilege and the effect on systems managed by FortiManager remain undisclosed.

Remediation

  1. Upgrade each affected branch to the corresponding supplied target: 8.0.0 to 8.0.1 or above; 7.6.0 through 7.6.7 to 7.6.8 or above; 7.4.0 through 7.4.5 to 7.4.6 or above; and 7.2.0 through 7.2.8 to 7.2.9 or above.
  2. Reconcile the post-upgrade inventory to confirm the actual version of every FortiManager and verify that no instance remains in an affected range.
  3. Until upgrading is possible, restrict access to the FGFM port to required management peers where operationally appropriate. This is a temporary risk-reduction precaution, not a confirmed workaround.
  4. Check service health and administrative changes after the upgrade. The available evidence does not provide a separate workaround or other specific mitigation guidance.

Detection

  1. Inventory every FortiManager instance and record its exact release branch and version, with priority given to versions in the affected ranges.
  2. Identify the network addresses and zones that can reach the FGFM port, including access from untrusted networks or third-party controlled segments.
  3. Review firewall, flow, and network detection telemetry for unexpected connections to the FGFM port or anomalous FGFM traffic during the period under review. This is a precautionary review, not a Fortinet-confirmed IOC.
  4. Check for unexpected FortiManager configuration changes, administrative activity, or service anomalies that could be consistent with unauthorized command execution.
  5. No specific log event or IOC is provided. Failure to find evidence in available logs does not prove that a system is safe.
Sources (16)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.