Contact us
← CVEHit Business AdvisoryFortiManager FGFM — CVE-2026-126261: Business Triage

CVEHit Business Advisory by IntegrityLab.ai

Published

FortiManager FGFM flaw may allow code execution without an account — CVE-2026-126261: Business Triage9.0/10Critical · CVSS 3Fortinet PSIRTFix available8.0.1+ for 8.0 groupCISA assessmentCVE.org sourceNo KEVChecked Nov 13

Update affected FortiManagers first where their FGFM service is reachable from untrusted networks. Research: CVE record and KEV checked November 13, 2026.

Check these three things.

  1. System owner: confirm each FortiManager runs its version group's fixed release or above, such as 8.0.1 for the 8.0 group.
    Fixed release for each version group
    • Provider: confirm the release of any FortiManager it runs for you.
    • FortiManager versions belong to version groups named by their first two numbers. For example, 7.4.5 is in the 7.4 group.
    • Fortinet lists these affected releases and fixes for CVE-2026-126261:
      • 8.0 group: 8.0.0 is affected. Update to 8.0.1 or above.
      • 7.6 group: 7.6.0 through 7.6.7 are affected. Update to 7.6.8 or above.
      • 7.4 group: 7.4.0 through 7.4.5 are affected. Update to 7.4.6 or above.
      • 7.2 group: 7.2.0 through 7.2.8 are affected. Update to 7.2.9 or above.
    • The CVE record lists FortiManager only. It marks releases outside these ranges as unaffected.
    • These releases fix CVE-2026-126261. Two related high-privilege flaws need later releases in some groups.
    • Record:
      • Installed release.
      • Source of that record.
      • Date checked.
    • An installed fix does not show whether the FortiManager was reached before the update.
  2. Network owner: confirm which networks can reach each FortiManager's FGFM service, which is separate from its web sign-in page.
    When the risk applies
    • No account is needed. Reach to the FGFM service is the condition.
    • FGFM is the service FortiManager uses to manage FortiGate firewalls. Fortinet's Device Manager uses it to add devices and install policy packages and device settings.
    • Affected interface:
      • Fortinet's advisory summary and the CVE record name the FGFM port as the required path.
      • The advisory's component field says GUI. The sources do not explain this label.
      • A reachable web sign-in page does not show that FGFM is reachable.
      • A blocked web sign-in page does not show that FGFM is blocked.
      • Still unknown until checked: which networks can reach FGFM on each FortiManager.
    • Fortinet's FortiManager 7.6 incoming-ports list names TCP/541 for IPv4 FGFM management. Confirm the port your deployment uses.
    • Fortinet documents FGFM designs that place FortiManager on the public internet. Only your records show whether yours is reachable.
    • Records to check:
      • Firewall rules in front of the FortiManager.
      • NAT and port-forwarding rules.
      • Cloud network access rules, if hosted in a cloud.
      • Provider statements, if a provider hosts it.
    • Limited FGFM reach lowers exposure. An affected release needs the fix even so.
  3. Security owner: review existing FortiManager records for unexpected management changes or managed-device activity.
    What the records can show
    • Records to review:
      • Existing FortiManager administrator logs.
      • Existing FortiManager event logs.
      • Devices added or provisioned.
      • Policy packages installed.
      • Device settings installed.
      • Changes on managed FortiGates that no approved change explains.
    • Cover the period when an affected release was reachable, including FortiManagers updated since.
    • Limits:
      • Fortinet's advisory gives no specific signs of attack.
      • A clean log is not proof of no change.
      • A missing log leaves the question unresolved.
      • An update does not rule out earlier harm.

If an affected FortiManager's FGFM service is reachable from untrusted networks, update it first. Review its management records even after the update.

Do Now

  • System owner: update each affected FortiManager to its version group's fixed release, such as 8.0.1 for the 8.0 group.
    Fixed releases and proof the update is done
    • Fixed releases for CVE-2026-126261 by group:
      • 8.0.1 or above for 8.0.0.
      • 7.6.8 or above for 7.6.0 through 7.6.7.
      • 7.4.6 or above for 7.4.0 through 7.4.5.
      • 7.2.9 or above for 7.2.0 through 7.2.8.
    • Update FortiManagers with reachable FGFM service first.
    • Record:
      • Installed release after the update.
      • Version group.
      • Source of the record.
      • Date checked.
    • The update does not show whether earlier harm occurred.
  • Network owner: decide whether to limit FGFM reach from untrusted networks until the update is done.
    Before changing access
    • This does not replace the update.
    • Fortinet's retrieved advisory names upgrades as the solution. It does not name this limit.
    • Managed FortiGates use FGFM for provisioning and policy installs. A limit that blocks them can interrupt management.
    • If reach is already limited, record that evidence.
    • Record:
      • FortiManager.
      • Networks that can reach FGFM.
      • Change made, if any.
      • Date checked.
  • Security owner: start response if FortiManager records show an unauthorized change or access.
    What to preserve and when to widen
    • Preserve existing FortiManager management records before reviewing them.
    • Start with FortiManagers whose FGFM service was reachable on an affected release.
    • Act on signs of unauthorized activity even if this CVE is not established as the cause.
    • Extend the review to managed devices when FortiManager records show an unexplained change.
    • Do not assume every managed device was changed.
    • Record:
      • Records reviewed.
      • Source of the records.
      • Period covered.
      • Date reviewed.
  • Operations owner: handle an unexplained FortiManager outage or managed-firewall disruption as a service incident.
    Alerts to review and when to escalate
    • Alerts to review:
      • Existing uptime alerts for FortiManager.
      • Existing network-service alerts for managed sites.
    • Send signs of unauthorized change to the Security owner.
    • An outage alone does not prove this CVE.
    • An outage alone does not prove a break-in.
    • Record:
      • Alerts reviewed.
      • Source of the alerts.
      • Date reviewed.

Do Next

  • System owner: plan fixes for two related high-privilege FortiManager flaws that need later releases in some groups.
    Releases for the related flaws
    • Both need a signed-in account with high privileges. They do not share the no-account condition of CVE-2026-126261.
    • CVE-2026-126227 fixed FortiManager releases:
      • 8.0.2 or above.
      • 7.6.8 or above.
      • 7.4.12 or above.
      • 7.2.13 or above.
    • CVE-2026-126231 fixed FortiManager releases:
      • 8.0.1 or above.
      • 7.6.8 or above.
      • 7.4.12 or above.
      • No 7.2 fix is listed.
    • For CVE-2026-126231, the description says all 7.2 versions are affected. Its structured ranges list 7.2.0 through 7.2.13. The sources do not settle this.
    • Releases listed as fixed for all three CVEs in their group:
      • 8.0.2 or above.
      • 7.6.8 or above.
      • 7.4.12 or above.
    • The 7.2 group has no release listed as fixing all three. System owner: ask Fortinet whether to move to another version group.
    • Both related records also list these products. Check them if you run them:
      • FortiAnalyzer.
      • FortiManager Cloud.
      • FortiAnalyzer Cloud.

Check your own records.

  • Use your approved AI tool.
  • Require evidence. Flag unknowns.

Read the prompt

The reported finding

Improper authorization in FortiManager FGFM (CVE-2026-126261)

Original advisory →
Required conditions
  • An affected FortiManager release.
  • An attacker who can reach the FGFM port. FGFM is the FortiGate-to-FortiManager management protocol.
  • No sign-in. Fortinet lists the attack type as Unauthenticated.
Reported outcome
  • Fortinet says the attacker may execute code or commands via crafted FGFM packets.
  • Fortinet's impact field: Execute unauthorized code or commands.
  • Fortinet says it discovered the flaw internally.
  • The advisory gives no signs of attack.
Rating and exploitation evidence
  • Fortinet's advisory reports CVSSv3 9.0, Critical.
  • The CVE record labels 9.0 as its CVSS 3.1 base score. Its vector also includes temporal parts: E:U/RL:O/RC:C. This brief shows Fortinet's reported 9.0 without recalculating it.
  • Fortinet's advisory, published November 10, 2026, states Known Exploited: No, as retrieved November 12, 2026.
  • KEV catalog 2026.11.13, released November 13, 2026 at 20:24:18 UTC, was checked at 21:35 UTC. It has no entry for this CVE or the two related CVEs.
  • CISA assessment in the CVE record, dated November 13, 2026 at 13:33 UTC (SSVC 2.0.3):
    • Exploitation: none.
    • Automatable: yes.
    • Technical Impact: total.
  • Exploitation: none means CISA had no evidence of exploitation in that assessment. It does not prove no attacks occurred or that your systems are safe. No KEV entry is not proof of no attacks.

Fix guidance

  • Fortinet lists a fixed release for each affected FortiManager version group.
    • 8.0 group: 8.0.1 or above.
    • 7.6 group: 7.6.8 or above.
    • 7.4 group: 7.4.6 or above.
    • 7.2 group: 7.2.9 or above.
  • These releases fix CVE-2026-126261. They do not fix every related FortiManager flaw:
    • CVE-2026-126227 fixed releases by version group:
      • 8.0 group: 8.0.2 or above.
      • 7.6 group: 7.6.8 or above.
      • 7.4 group: 7.4.12 or above.
      • 7.2 group: 7.2.13 or above.
    • CVE-2026-126231 fixed releases by version group:
      • 8.0 group: 8.0.1 or above.
      • 7.6 group: 7.6.8 or above.
      • 7.4 group: 7.4.12 or above.
      • No 7.2 fix is listed.
  • A current fixed release shows today's status. Earlier reach to FGFM on an affected release still calls for the records review.

What IntegrityLab.ai can check

  • IntegrityLab.ai's authorized web discovery records these details from web services:
    • Response status.
    • Page title.
    • Content length.
    • Server identification.
  • Limits:
    • No check for CVE-2026-126261 was found in the current assessor code.
    • It does not check FGFM reachability.
    • No web check establishes reach to a non-web management service such as FGFM.
    • It does not establish:
      • Installed release.
      • Fix status.
      • Configuration.
      • Compromise.
    • A front server can hide the system behind it. Missing identification does not rule FortiManager out.
  • A web observation can point an owner to a service worth checking. A visible FortiManager sign-in page does not show FGFM reach or this flaw.

How to read the score

Fortinet PSIRT CVSS 3: 9.0 (Critical). Use the conditions and update history alongside the score to set your priorities.

Sources and vendor guidance

Need an independent review of your public exposure?

See IntegrityLab.ai →

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…