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: numeric truncation error in BGP daemon (CVE-2026-126254) fixed in 7.2.14, 7.4.13, 7.6.8 and 8.0.2

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

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

CVE-2026-121528 CVE-2026-121530 CVE-2026-126253 CVE-2026-126254 CVE-2026-126255 CVE-2026-126256 CVE-2026-126258 CVE-2026-126259

Published 13/11/2026 09:09

Timeline

2 events over 3 d

  1. 10/11/2026 09:00ConfirmedFortinet PSIRT+3 d
  2. 13/11/2026 09:09Published on WatchtowerPro CISO

In short

A configured iBGP neighbor can send crafted or malformed BGP attributes to all connected routers on FortiOS and FortiSASE, which can disrupt routing. Fortinet rates it Critical (CVSS 9.6). Upgrade FortiOS to 7.2.14, 7.4.13, 7.6.8 or 8.0.2 (or later); affected FortiSASE versions must migrate to a fixed release. 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 controls a trusted iBGP neighbor can send crafted routing data that disrupts routers connected to the affected device, needing a working iBGP session.

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

Severity score

9.8of 10Critical

The worst of 8 CVEs · 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

  • Read the data it holds
  • Change or delete that data
  • Take it offline

Type: denial of service.

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 to 8.0.1
  • FortiOS 7.6.0 to 7.6.7
  • FortiOS 7.4.0 to 7.4.12
  • FortiOS 7.2.0 to 7.2.13
  • FortiSASE 26.2, 26.1, 25.4, 25.3, 25.2, 25.1.a and 25.1 (all versions); the advisory says to migrate to a fixed release
  • Exposed devices are those running BGP with configured iBGP neighbors

Fixed in

  • 8.0 branch: 8.0.2
  • 7.6 branch: 7.6.8
  • 7.4 branch: 7.4.13
  • 7.2 branch: 7.2.14

What to do now

  • Upgrade FortiOS to the fixed version for your branch: 7.2.14, 7.4.13, 7.6.8 or 8.0.2 (or later). Fortinet's upgrade tool is at docs.fortinet.com/upgrade-tool.
  • Prioritise devices that run BGP with iBGP neighbors.
  • FortiSASE 26.3.1 and 26.3.1_a were fixed by Fortinet in 26.3.2 and need no customer action; other affected FortiSASE versions must migrate to a fixed release.
  • Fortinet publishes no workaround. Any interim measure only reduces exposure and does not make the device safe: check that every iBGP neighbor is trusted, restrict BGP sessions to known peers and watch for BGP daemon crashes.

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, 4 open questions, followed up as sources answer and all 7 sources 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

Broken Access Control in Two-Factor-Authentication Vendor · Improper neutralization of special elements in output used by a downstream component in sshd Vendor · Numeric truncation error 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.