ReconXWatchtower

Where this stands

First reported 10/11/2026 09:00

  1. 1Unconfirmednot observed
  2. 2Corroboratednot observed
  3. 3Confirmed now10/11/2026 09:00Fortinet PSIRT
  4. 4Exploitednot yet

Unconfirmed and Corroborated were never seen on its own: the first report we had was already stronger.

FortiOS: missing authentication flaw in HA (CVE-2026-126259) fixed in 8.0.1, 7.6.8, 7.4.13 and 7.2.14

Fortinet FortiGate (FortiOS) · Critical (CVSS 9.8)Fix available

≈450,000internet-facing systems run Fortinet FortiGate (FortiOS)Shodan estimate · 17/11/2026

CVE-2026-126259

Published 16/11/2026 20:14

Timeline

2 events over 6 d 11 h

  1. 10/11/2026 09:00ConfirmedFortinet PSIRT+6 d 11 h
  2. 16/11/2026 20:14Published on WatchtowerPro CISO

In short

An unauthenticated attacker who can send crafted high-availability (HA) packets to a FortiOS device using HA FGSP with standalone-config-sync, or autoscale, may be able to run commands as super admin. Fortinet confirms the flaw (CVE-2026-126259) in advisory FG-IR-26-273. Update to FortiOS 8.0.1, 7.6.8, 7.4.13 or 7.2.14; FortiOS 7.0 has no fix and must be migrated. Shodan estimates about 450,452 internet-facing Fortinet FortiGate (FortiOS) servers worldwide, 76,587 of them in the EU (17/11/2026); how many run an affected version is not yet known.

How bad is it

Critical. An attacker who can send crafted high-availability packets to a vulnerable FortiGate may be able to run commands with full administrator rights, without logging in.

Confirmed by the vendor or a CERT - no exploitation reported yet.

Severity score

9.8of 10Critical

CVSS 3.1 from NVD, from fortinet.com, read 16/11/2026.

What an attacker needs

  • Internet access to itEnough
  • A loginNot needed
  • A user to clickNo
  • Special settingsNo

Red helps the attacker, blue holds them back, grey is not published yet.

If it works, an attacker can

  • Run their own code on the system
  • Read the data it holds
  • Change or delete that data
  • Take it offline

Type: remote code execution.

A score is the worst case for the flaw, not a verdict on any one system. How we score · ReconX customers see which of their own systems are affected.

Affected versions

  • FortiOS 8.0.0
  • FortiOS 7.6.0 to 7.6.7
  • FortiOS 7.4.0 to 7.4.12
  • FortiOS 7.2.0 to 7.2.13
  • FortiOS 7.0: all versions
  • Fortinet names two exposed setups: HA with FGSP plus standalone-config-sync, and autoscale. The advisory read does not say whether a plain HA cluster without these features is affected.

Fixed in

  • 8.0 branch: 8.0.1
  • 7.6 branch: 7.6.8
  • 7.4 branch: 7.4.13
  • 7.2 branch: 7.2.14
  • 7.0: no fix

What to do now

  • Update FortiOS to the fixed version for your branch: 8.0.1 or above, 7.6.8 or above, 7.4.13 or above, or 7.2.14 or above. Fortinet's upgrade path tool is at https://docs.fortinet.com/upgrade-tool.
  • If you run FortiOS 7.0, no fixed release exists; Fortinet says to migrate to a fixed release on a newer branch.
  • Until the update is installed, Fortinet says the virtual patch FG-VD-61445.0day (FMWP database update 26.082) is available; check with Fortinet whether it covers your product and licence.
  • Interim measures reduce exposure and do not make a device safe; only the update fixes the flaw.
  • Check whether your devices use HA FGSP with standalone-config-sync or autoscale, as these are the setups Fortinet names.

ReconX customers see the full notice - and their own systems

Our customers are alerted at every phase. Until a patch exists, the ReconX agent watches their servers from the inside for anomalies, and our outside view - the attacker's view - shows which systems to fix first.

In ReconX: the full analysis, 5 open questions, followed up as sources answer and all 1 source with their dates. And technology matching: which of your systems run Fortinet FortiGate (FortiOS), at which version, fixed or not - and what each one needs.

Sign in to ReconXAbout ReconX

Main sources

Unauthenticated adjacent command execution via HA Vendor

Data: Shodan - Fortinet FortiGate (FortiOS) (estimate, 17/11/2026)

← All Watchtower notices

Pro CISO publishes ReconX Watchtower notices from public sources so organisations can act early. A notice describes an issue, never any organisation's systems. Times are Amsterdam time. Report a vulnerability in our systems.

ReconX Watchtower opened to the public on 24 October 2026, in the wake of PHP2Shell - our contribution to a safer digital ecosystem.