Skip to content

NetworksCritical 9.8

CVE-2026-126259

Unauthenticated HA flaw in FortiOS allows super-admin command execution

How scary is it?

updated 22 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • None known

    Public exploit code is out

    None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list2

    Not in the catalog as of our last sync.

Scare-o-meter

Act this week

Serious and within reach of attackers. Schedule the fix this week.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: Reachable over the network with no login and no user action; CVSS 9.8.1 Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run Fortinet FortiOS in an affected version8.0.0 / >= 7.6.0 and <= 7.6.7 / >= 7.4.0 and <= 7.4.12 (+2 more)

    8.0.0 >= 7.6.0 and <= 7.6.7 >= 7.4.0 and <= 7.4.12 >= 7.2.0 and <= 7.2.13 >= 7.0.0 and <= 7.0.19

    The CVE record states no fixed release.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Recommendation, AI-writtenApply vendor patch ASAP; if unavailable, disable HA FGSP/config-sync and isolate HA/autoscale links.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. Unauthenticated remote admin command execution in widely deployed FortiOS; allows full firewall takeover and network control — high-impact across enterprises and service providers.

CVSS
9.8Critical
Exploited in the wild
Not knownnot in CISA KEV as of our last sync
EPSS
0.60%chance of exploitation in the next 30 daystop 51% of scored CVEsFIRST score of 21 Nov 2026
Fix
Not stated by the vendorno fixed release in the CVE record
Published
11 Nov 2026analysed here 14 Nov 2026

Summary

Impact

Unauthenticated attacker can send crafted HA packets to execute commands as super-admin, leading to full device compromise and network control.

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Fortinet FortiOS8.0.0>= 7.6.0 and <= 7.6.7>= 7.4.0 and <= 7.4.12>= 7.2.0 and <= 7.2.13>= 7.0.0 and <= 7.0.19Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • FortiOS 8.0.0
  • FortiOS 7.6.0 - 7.6.7
  • FortiOS 7.4.0 - 7.4.12
  • FortiOS 7.2.0 - 7.2.13
  • Features: HA FGSP, standalone-config-sync, autoscale

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? No. A function is missing its authentication check. The attack requests look like normal traffic, so a WAF has nothing to match on.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC
exploitation none, automatable yes, technical impact totalAssessed by CISA 12 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

  1. 11 Nov 2026Published
  2. 12 Nov 2026CISA SSVC assessment: exploitation nonesame day later
  3. 13 Nov 2026CVE record last updated1 day later
  4. 14 Nov 2026Analysed by vulneraibility.com2 days later

Common questions

Is CVE-2026-126259 being exploited?

Not confirmed. CVE-2026-126259 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.60% probability of exploitation in the next 30 days.

How severe is CVE-2026-126259?

CVE-2026-126259 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-126259?

Not known from our data. No patch reference has been recorded for CVE-2026-126259, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-126259 affect?

CVE-2026-126259 affects FortiOS 8.0.0, FortiOS 7.6.0 - 7.6.7, FortiOS 7.4.0 - 7.4.12, FortiOS 7.2.0 - 7.2.13, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-126259?

Apply vendor patch ASAP; if unavailable, disable HA FGSP/config-sync and isolate HA/autoscale links.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

1 reference in the CVE record, grouped by the tags the record gives them.

Other links (1)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.