Fortinet published a security advisory on Tuesday, November 10, 2026, for a critical flaw in FortiManager. The flaw is tracked as CVE-2026-126261 and Fortinet gives it a CVSSv3 score of 9.0.
What the flaw is
Fortinet titles the advisory "FGFM elevation before registration password is verified." According to the advisory, an improper authorization problem lets an attacker who has no login, but can reach the FGFM port, send crafted FGFM packets and run unauthorized code or commands.
The advisory lists the issue as not known to be exploited, and it lists no workaround. Fortinet says the flaw was found internally by its own security team.
Which versions to upgrade
Fortinet lists these FortiManager versions as affected, with the first fixed release for each:
- 8.0.0: upgrade to 8.0.1 or above
- 7.6.0 through 7.6.7: upgrade to 7.6.8 or above
- 7.4.0 through 7.4.5: upgrade to 7.4.6 or above
- 7.2.0 through 7.2.8: upgrade to 7.2.9 or above
A FortiOS fix the same day
On the same date Fortinet also published FG-IR-26-270 for CVE-2026-126256, an out-of-bounds read in the FortiOS kernel rated High with a CVSSv3 score of 7.4. Fortinet says it can lead to execution of unauthorized code or commands and lists it as not known to be exploited. Fixed releases are FortiOS 8.0.2, 7.6.8, 7.4.13 and 7.2.14 or above. For FortiSASE, Fortinet says it already fixed versions 26.3.1 and 26.3.1_a in 26.3.2, so those customers need no action, while customers on 26.2 and older should move to a fixed release. Fortinet also lists a virtual patch for this flaw.
Who should act
Teams that run FortiManager should check their version against the list above and plan the upgrade, and should know which networks can reach the FGFM port. Tracking advisories like these, matching them to the versions actually installed and confirming the fix is daily work for a network security specialist and a system administrator.
If you are preparing for those roles, our Certification Path Planner shows which certifications fit each one.
