Free delivery

GGuestNot signed in
You're not signed in
LoginCreate account

11/16/2026 • Security

FortiOS BGP Flaw Scores 9.6: Does It Affect Your Network?

Fortinet has patched CVE-2026-126254, a FortiOS routing flaw rated 9.6 that lets a trusted iBGP neighbour pass malformed route data on to every connected router. Many small networks never switch BGP on, so here is how to check whether yours does and what to do if so.

On 10 November 2026, Fortinet published a fix for a FortiOS flaw rated 9.6 out of 10, in a feature that many small-business firewalls never switch on. The bug sits in BGP, the routing protocol that larger and multi-site networks use to tell each other where traffic should go. A neighbouring router that the firewall has been set up to trust can send it malformed routing information, which then travels on to every other router connected to it.

The flaw is tracked as CVE-2026-126254 (Fortinet advisory FG-IR-26-268). Whether it matters to you comes down to one question: does your FortiGate run BGP at all? The rest of this post is about answering that, and what to do if the answer is yes.

What happened, in plain English

Fortinet describes the bug as a numeric truncation error (CWE-197) in the FortiOS BGP service. Truncation is what happens when software stores a number in a space too small to hold it and the top part is cut off. The software then works with a different value from the one it was sent, and behaves in ways nobody intended.

In this case, Fortinet says the error may allow a configured iBGP neighbour to send malicious or malformed attributes to all connected routers using a specially crafted request. iBGP is the internal form of BGP, used between routers inside one organisation. Attributes are the details attached to each route as it is advertised.

Three nuances matter here.

  • It is not an anonymous attack from the internet. The CVSS vector lists privileges required as low (PR:L), and Fortinet classes the attack as authenticated. The sender has to be a router your firewall is already configured to peer with. An attacker would need to control one of those devices first.
  • The impact is disruption, not data theft. Fortinet lists the impact as denial of service. The vector rates confidentiality impact as none, and integrity and availability impact as high.
  • It is not known to be exploited. Fortinet's advisory marks it as not exploited in the wild, and it was not in CISA's Known Exploited Vulnerabilities catalogue when we checked on 16 November 2026.

On the score itself: the 9.6 is Fortinet's own rating, published through the NVD. The NVD entry was still awaiting NIST's independent analysis when we checked, so there is no second opinion on the number yet.

Why a bug that needs a trusted neighbour still scores 9.6

The score is high because of where the damage lands. The CVSS vector marks the scope as changed, which means the harm reaches beyond the device with the bug. The malformed data does not stop at the firewall that receives it. Per Fortinet's description, it goes on to all connected routers.

That is the nature of routing protocols. They exist so that routers can pass information along without a person approving each update. One compromised or misbehaving branch device can therefore affect the routing of every site that shares the same BGP mesh.

Affected versions and fixes

From Fortinet's advisory and the NVD entry:

FortiOS branchAffectedFixed in
8.08.0.0 to 8.0.18.0.2 or later
7.67.6.0 to 7.6.77.6.8 or later
7.47.4.0 to 7.4.127.4.13 or later
7.27.2.0 to 7.2.137.2.14 or later

Fortinet's advisory also lists FortiSASE. It says the 26.3 release was fixed by Fortinet in 26.3.2 with no customer action needed, and gives separate guidance for older FortiSASE releases. If you use FortiSASE, check the advisory for your release.

Does this affect a small business?

A single-site office with one FortiGate and one internet connection usually relies on static routes and has no BGP configured. If that describes your network, this flaw has no path to you. You should still take the firmware update, because the same releases fix other issues, including the high-availability flaw we covered separately.

The businesses that should look more closely are those with several sites. Multi-site Fortinet SD-WAN designs commonly use iBGP between the head office and the branches, often set up by an IT provider and not always documented for the business owner. BGP also turns up on links to data centres and cloud providers. If any of that applies, your FortiGate may have iBGP neighbours you have never been told about.

The real lesson: trusted is not the same as safe

A firewall is built to be suspicious of the internet. Its routing neighbours get much less scrutiny, because they were configured as trusted. That trust is only as good as the weakest device in the mesh. A small branch router that has missed a few updates, or a forgotten device nobody is watching, becomes a way to disrupt every site at once.

It is worth knowing which devices your firewall listens to, as well as which ones it blocks.

The honest bit

Fortinet has featured in this series before, including our FortiBleed explainer, and it would be easy to make this a pile-on. That would be unfair. No vendor is immune, including the ones we like and sell. Every routing implementation has had bugs of this kind. Fortinet's advisory credits its own product security team with finding this one, and fixes for every affected branch were listed when it was published.

The practical difference between platforms is how the fix reaches the device. With a traditionally managed firewall, someone has to notice the advisory, plan the upgrade and carry it out. Platforms where the vendor delivers firmware updates for you shorten that gap. That is not a reason to replace anything. It is a reason to be sure somebody owns patching on whichever platform you run.

What we'd suggest you actually do

  1. Find out whether BGP is in use. Ask your IT provider, or look under the routing settings in the FortiGate interface. From the command line, get router info bgp summary lists any BGP neighbours. No neighbours means this flaw does not apply to that device.
  2. Check your FortiOS version. It is shown on the dashboard. Compare it with the table above.
  3. Plan the upgrade. Move to 8.0.2, 7.6.8, 7.4.13 or 7.2.14 or later, depending on your branch. Fortinet's upgrade path tool shows the supported steps from your current version. Schedule it out of hours, and take a configuration backup first.
  4. If you do run iBGP, review the neighbours. Confirm that each one is a device you know about, still need and keep patched. Remove any peering left over from an old site or a retired link.
  5. Patch the branches too. In a multi-site network, the small device at the smallest site is part of the same mesh. Bring them all to a fixed release.
  6. Keep the basics in order. Unique admin credentials, MFA on management access, and some way of noticing unusual behaviour on the network.

The friendly takeaway

A 9.6 next to a firewall's name is alarming, but the number describes the worst case and not your network. For this flaw, the worst case needs BGP to be running and a trusted neighbour to be under someone else's control. Many small businesses will find they are not exposed and can apply the update at the next maintenance window. Multi-site businesses should check sooner.

If you are not sure which group you are in, or you would like a second pair of eyes on a routing configuration someone else set up, get in touch. We are happy to help you work it out, with no hard sell.

References

Contact Us

Email: [email protected]

Phone: 1300 989 334

About

Your one-stop technology hub for all your networking, security, and IT needs. From cutting-edge networking solutions to robust security products, we provide everything your business requires to stay connected, secure, and efficient. Whether you're looking for advanced hardware, software, or services, we offer reliable, innovative technology tailored to help you build and protect your digital infrastructure.

Copyright © 2026 TYONLINE TECHNOLOGY PTY. LTD. All Rights Reserved.