Automated Threat Modeling

Brief Summary: FortiManager CVE 2026 126261, Unauthenticated Improper Authorization in FGFM Allowing Code or Command Execution

A brief summary of CVE 2026 126261, an improper authorization flaw in the FortiManager FGFM listener that may let an unauthenticated attacker who can reach the FGFM port execute code or commands. Includes affected versions and patch information from Fortinet advisory FG IR 26 275.

CVE Analysis

6 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Brief Summary: FortiManager CVE 2026 126261, Unauthenticated Improper Authorization in FGFM Allowing Code or Command Execution

Introduction

Fortinet has fixed a flaw in FortiManager that lets a peer on the FGFM management channel reach a privileged protocol state before its registration password is checked, which may allow an unauthenticated attacker to execute code or commands. FortiManager is the system that centrally configures and pushes policy to fleets of FortiGate devices, so a weakness in the service those devices use to register with it deserves prompt attention from anyone running the affected branches.

The issue is tracked as CVE 2026 126261 and was published in Fortinet advisory FG IR 26 275 on November 10, 2026. Fortinet rates it Critical with a CVSS v3 score of 9.0 and the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C. The CVE data we received lists a score of 9.8. The Fortinet advisory and CVE record both report 9.0, so we treat 9.0 as the supported figure.

Technical information

Background: what FGFM does

FGFM is the protocol FortiGates use to register with, and then be managed by, FortiManager. On the FortiManager side it is served by a listener on TCP 541. In a normal flow, a FortiGate connects to that listener and presents its registration credentials. Only after verification is it allowed to participate in the privileged management functions of the protocol.

Root cause

Fortinet titled the advisory "FGFM elevation before registration password is verified." That title, together with the assigned weakness class CWE 285 (Improper Authorization), describes an ordering bug in the FGFM listener:

  • Before the fix, a connecting peer could reach a privileged protocol state before FortiManager had verified the registration password.
  • Because privileged FGFM handlers were reachable from that state, a crafted FGFM packet from an unauthenticated attacker could lead to code or command execution.
  • The fixed builds should verify the registration password first, and only then allow the session to elevate or reach privileged FGFM handlers. Authentication must complete before authorization is granted.

FortiManager is closed source, and Fortinet has not published implementation details, packet layouts, a proof of concept, or any code. The description above is inferred from the advisory title and the CWE, not from vendor code. The CVE record excerpt reviewed in our briefing also showed a single CWE entry without exposing the identifier, so the CWE 285 mapping comes from the supplied CVE data.

Scoring characteristics

The published vector records network attack access, low attack complexity, no required privileges, no user interaction, unchanged scope, and high impact to confidentiality, integrity, and availability. The E:U temporal component reflects that, at publication, no exploit code was known. These values describe how the flaw is scored. They are not incident telemetry.

Attack flow

Based on the advisory, the attack path looks like this at a high level:

  1. The attacker identifies a FortiManager whose FGFM listener (TCP 541) is reachable from the attacker's network position.
  2. The attacker opens an FGFM session without valid registration credentials.
  3. The attacker sends crafted FGFM packets that move the session into a privileged protocol state before the registration password has been verified.
  4. With privileged FGFM handlers now reachable, the attacker may execute code or commands on the FortiManager.

The sources do not describe how the packets are constructed or which handlers are abused. The main prerequisite is network reachability to the FGFM port. No credentials and no user interaction are required.

Patch information

Fortinet fixed this in firmware only. There is no public commit, diff, or code snippet. The fix is the set of fixed FortiManager builds listed in Fortinet advisory FG IR 26 275, published November 10, 2026. Fixed versions, from the live advisory as fetched again on November 11, 2026:

  • FortiManager 8.0: affected 8.0.0; fixed in 8.0.1 or above
  • FortiManager 7.6: affected 7.6.0 through 7.6.7; fixed in 7.6.8 or above
  • FortiManager 7.4: affected 7.4.0 through 7.4.5; fixed in 7.4.6 or above
  • FortiManager 7.2: affected 7.2.0 through 7.2.8; fixed in 7.2.9 or above

Points to know before deploying:

  • The release notes do not mention it. The public 7.6.8 resolved issues page lists functional bugs (Device Manager, Policy and Objects, VPN Manager and others) and has no FGFM or CVE entry. Confirm protection by checking your build number against the list above, not by searching changelogs.
  • Sources disagree on 7.4 and 7.2. A third party summary from InfoSec Monkey published November 10, 2026 said there was no fix for 7.4 and 7.2 and recommended migrating to 7.6.8. The live Fortinet advisory now lists 7.4.6 and 7.2.9 as fixed, and the vendor advisory is authoritative. Because 7.4.6 and 7.2.9 were released well before this disclosure, check the advisory's current wording and ask Fortinet support if you plan to stay on those branches. Moving to the latest 7.6 build avoids the question.
  • There is no virtual patch. The advisory states no IPS virtual patch exists. The firmware upgrade is the only vendor fix.
  • Configuration is not a substitute. The FGFM deny unknown setting introduced as hardening after the FortiJump vulnerability (CVE 2024 47575) is still useful. This flaw is triggered before the registration password is checked, though, and Fortinet lists no workaround, so that setting does not replace the upgrade.
  • Upgrade in the right order. Upgrade FortiManager before the FortiGates it manages, use Fortinet's upgrade path tool when moving between major branches, and take backups before updating.
  • Where the fix is tracked. The GitHub advisory GHSA 952j p3c7 fpqx has not been reviewed and lists no patched package versions. NVD links only to the Fortinet advisory. Use FG IR 26 275 for fixed versions.

As an exposure check (not a Fortinet confirmed workaround), review which networks can reach the FGFM port on your FortiManager instances while upgrades are scheduled.

Affected systems and versions

  • 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

The vulnerable condition is network reachability of the FGFM listener (TCP 541) by the attacker. No authentication or user interaction is required.

Vendor security history

FortiManager's FGFM service has had a serious issue before: the FortiJump vulnerability, CVE 2024 47575, which led to the FGFM deny unknown hardening setting referenced in the patch guidance above.

More broadly, a 2025 CISA alert described a threat actor creating a malicious file using previously exploited FortiGate vulnerabilities, naming CVE 2024 21762, CVE 2023 27997, and CVE 2022 42475. CISA said the file could enable read only access to device files, potentially including configurations. That activity involved FortiGate and different vulnerabilities. It is not evidence of exploitation of CVE 2026 126261 or FortiManager.

For this CVE specifically, Fortinet's advisory lists Known Exploited: No, and the reviewed sources name no threat actor, campaign, or indicators of compromise. Treat that as the vendor's status at publication and recheck the live advisory during response.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization