Fortinet has published security advisory FG-IR-26-268 describing the critical vulnerability CVE-2026-126254 in the BGP daemon of FortiOS and FortiSASE. This Numeric Truncation Error vulnerability (CWE-197) with a CVSSv3 score of 9.6 allows a configured iBGP neighbor to send malicious or incorrect routing attributes to all connected routers via a specially crafted request. Four FortiOS branches (from 7.2 to 8.0) and numerous FortiSASE versions are affected. Fixes are already available — organizations using BGP peering on Fortinet equipment need to prioritize upgrading.
Nature of the vulnerability
The vulnerability falls into the class of numeric truncation errors (Numeric Truncation Error). In the context of the BGP daemon, this means that when processing certain numeric values in BGP message attributes, data is lost due to casting to a lower-precision type. An authenticated iBGP neighbor (that is, a router already configured as a trusted peer within the autonomous system) can exploit this flaw to propagate corrupted attributes to all connected routers. According to the advisory, the impact is classified as denial of service (DoS).
The key point is that exploitation requires authentication and an established iBGP peering relationship. This narrows the pool of potential attackers but at the same time increases the blast radius — malicious attributes can cascade across the entire BGP topology connected to the vulnerable device. For organizations using FortiGate as a BGP router in the network core, the consequences may include routing disruption across the entire infrastructure.
According to the Fortinet advisory, at the time of publication the vulnerability is not classified as being actively exploited (Known Exploited: No). However, no independent confirmation of this statement has been found — no public evidence of exploitation or PoC code has been identified either.
Affected versions and fixes
FortiOS
- FortiOS 8.0: versions 8.0.0–8.0.1 are affected → update to 8.0.2 or later
- FortiOS 7.6: versions 7.6.0–7.6.7 are affected → update to 7.6.8 or later
- FortiOS 7.4: versions 7.4.0–7.4.12 are affected → update to 7.4.13 or later
- FortiOS 7.2: versions 7.2.0–7.2.13 are affected → update to 7.2.14 or later
FortiSASE
- FortiSASE 26.3.1 and 26.3.1_a: fixed in version 26.3.2 — Fortinet has performed the upgrade automatically; no action is required from customers
- FortiSASE 26.2, 26.1, 25.4, 25.3, 25.2, 25.1.a, 25.1: all versions are affected — migration to a fixed release is required
- FortiSASE 24.4 and earlier (24.3, 24.1, 23.x, 22.4): not affected
For upgrade planning, Fortinet provides an upgrade planning tool.
Impact assessment
The highest risk is to organizations where Fortinet devices act as BGP routers with configured iBGP sessions. This is typical for large enterprise networks, managed service providers, and telecom operators using FortiGate as edge or core routers. The CVSS score of 9.6 reflects the high potential for cascading impact: compromising a single BGP peer can cause denial of service across all interconnected routers.
For environments without configured iBGP peering, the vulnerability does not pose an immediate threat — the attack vector is tied to a specific configuration. Nonetheless, the broad range of affected versions (four major FortiOS branches) means that a significant portion of the installation base is potentially vulnerable.
Recommendations
- Determine upgrade priority for FortiGate devices with configured iBGP sessions. These are the systems that lie directly on the exploitation path.
- Upgrade FortiOS to the fixed versions: 8.0.2, 7.6.8, 7.4.13, or 7.2.14, depending on the branch in use.
- For FortiSASE: if you use versions 25.1–26.2, plan migration to a fixed release. Users of FortiSASE 26.3.1/26.3.1_a are already protected by the automatic upgrade to 26.3.2.
- Apply a virtual patch as a temporary measure: Fortinet provides the virtual patch FG-VD-62507.0day. in FMWP database update version 26.118. This allows you to protect devices until the firmware is fully upgraded.
- Audit your BGP configuration: review the list of configured iBGP neighbors and make sure that all peers are trusted and legitimate devices.
We have previously analyzed vulnerabilities in Fortinet products — in particular, a critical RCE in FortiSIEM and an SQL injection in FortiMail. The current vulnerability has a different vector — it affects the routing plane rather than the web management interface, which makes it particularly dangerous for network infrastructure.
Organizations with BGP peering on Fortinet devices should treat upgrading as urgent: despite the absence of confirmed exploitation, the CVSS score of 9.6 and the potential for cascading routing failure make delay unjustified. Start by applying the virtual patch FG-VD-62507.0day. from FMWP update 26.118, and then schedule a firmware upgrade for the next available maintenance window.












