Skip to content
TEN Brief Ten verified stories a day 2026.11.16 KO

이 기사는 한국어로도 읽을 수 있습니다 →

Tech · 16 min read · Explainer

CVE-2026-126253 FortiOS patch versions — 7.6.8 and 7.4.13 shipped 19 days before the advisory

CVE-2026-126253 in Fortinet FortiOS is fixed in FortiOS 8.0.2, 7.6.8, 7.4.13 and 7.2.14 or later; the 7.0 branch gets no fix and must move to a fixed branch. The flaw is an authentication bypass (CVSS 9.3) in the OSPF routing daemon of FortiOS and FortiSASE that lets an attacker on the same network segment broadcast forged routing information (LSAs) without logging in. Devices that do not run OSPF are not exposed to this path. Fortinet published advisory FG-IR-26-267 on November 10, 2026 (US time), but it had shipped the fixed builds 19 days earlier, on October 22. The advisory marks the flaw as not known to be exploited, and it is absent from the November 13, 2026 version of the US Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities (KEV) catalog.

A network engineer seen from behind checking rack-mounted firewall appliances with a laptop in a sunlit network room

The three lines

  • Versions — FortiOS 8.0.2, 7.6.8, 7.4.13, 7.2.14 or later. 7.0 has no fix and must migrate. Builds shipped October 22; the advisory followed on November 10
  • Conditions — only devices running OSPF, and the attacker must sit on the same network segment. No login is needed. At 9.3 it is not the highest score in the batch
  • Status — not exploited per Fortinet, not in CISA KEV as of the November 13 version. FortiMail and FortiManager carry separate 9.8-rated flaws from the same day

Key questions

CVE-2026-126253 FortiOS patch version
**FortiOS 8.0.2, 7.6.8, 7.4.13 and 7.2.14 or later. The 7.0 branch has no fixed build.** | Branch | Affected | Fixed | |---|---|---| | FortiOS 8.0 | 8.0.0–8.0.1 | 8.0.2 or later | | FortiOS 7.6 | 7.6.0–7.6.7 | 7.6.8 or later | | FortiOS 7.4 | 7.4.0–7.4.12 | 7.4.13 or later | | FortiOS 7.2 | 7.2.0–7.2.13 | 7.2.14 or later | | FortiOS 7.0 | 7.0.1–7.0.19 | No fix; migrate to a fixed branch | | FortiSASE 26.3 | 26.3.1, 26.3.1_a | Remediated by Fortinet in 26.3.2; no customer action |
Does CVE-2026-126253 require authentication
**No login is required. The device must be running OSPF, and the attacker must be on the same network segment.** | Item | Detail | |---|---| | Type | Authentication bypass by primary weakness (CWE-305) | | Location | OSPF daemon in FortiOS and FortiSASE | | CVSS 3 | 9.3 (Critical) | | Attack vector | Adjacent network (AV:A); not directly reachable from the internet | | Authentication | None | | Impact | Forged LSAs broadcast; integrity and availability high, confidentiality none | | Workaround in the advisory | None |
Fortinet November 2026 security updates exploited in the wild
**Fortinet marks them as not known to be exploited, and none of the batch appears in the November 13, 2026 version of CISA's KEV catalog.** | Date (US time) | Event | |---|---| | October 21 | Fortinet announces a security hardening release; FortiMail and FortiAuthenticator builds ship | | October 22 | FortiOS, FortiManager and FortiAnalyzer builds ship | | November 10 | 89 advisories published (nearly 100 vulnerabilities, about 17 critical) | | November 13 | Fortinet adds virtual-patch details to the BGP advisory; KEV version of this date lists none of the batch |

CVE-2026-126253, a routing flaw in Fortinet's firewall operating system FortiOS, is fixed in FortiOS 8.0.2, 7.6.8, 7.4.13 and 7.2.14. Fortinet disclosed it in advisory FG-IR-26-267 on November 10, 2026 (US time, the second Tuesday of the month), but the fixed builds had been available since October 22, nineteen days earlier. In October the company told customers to upgrade quickly without saying what had been fixed; on November 10 it published 89 advisories at once and the details came out.

The score is CVSS 9.3, in the critical band. Ordering work by that number alone would be a mistake. The flaw applies only to devices running the OSPF routing protocol, and the attacker has to be inside the same network segment. The same batch contains 9.8-rated flaws in FortiMail and FortiManager that are reachable without a login and, in FortiMail's case, without any special configuration. This piece sets out which version to move to, how to tell whether a device is in scope, and what exposure can be reduced when an upgrade has to wait, based on the text of Fortinet's advisories.

1. Which versions are fixed — 8.0.2, 7.6.8, 7.4.13, 7.2.14, and nothing for 7.0

The version table in FG-IR-26-267 reads as follows. Red Tiger Security, Rescana and Penligent give the same numbers (nFlo gives the same affected ranges only), and they match the version table Fortinet posted on its blog on October 21.

BranchAffectedAction
FortiOS 8.08.0.0–8.0.1Upgrade to 8.0.2 or later
FortiOS 7.67.6.0–7.6.7Upgrade to 7.6.8 or later
FortiOS 7.47.4.0–7.4.12Upgrade to 7.4.13 or later
FortiOS 7.27.2.0–7.2.13Upgrade to 7.2.14 or later
FortiOS 7.07.0.1–7.0.19No fix; migrate to a fixed release
FortiSASE 26.326.3.1, 26.3.1_aRemediated by Fortinet in 26.3.2; no customer action
FortiSASE 25.1–26.2All versions of each branchMigrate to a fixed release
FortiSASE 24.4 and earlierNot affected—

Three places in this table trip people up.

First, the 7.0 branch is not being fixed. The advisory lists 7.0.1 through 7.0.19 as affected and offers only "migrate to a fixed release". A device still on 7.0 has to change branch, to 7.2.14 or later. An alert from Rwanda's National Cyber Security Authority (NCSA) dated November 13 lists 7.0.18 or above among fixed versions, but no such version appears in Fortinet's advisory, and the advisory is the one to follow. Why an aging branch stops receiving patches is covered in our explainer on end of life (EOL).

Second, 7.4.12 means opposite things on different products. On FortiOS, 7.4.12 is still vulnerable and 7.4.13 is the fix. On FortiManager and FortiAnalyzer, which received advisories the same day, 7.4.12 is the fixed build for several flaws. A team running firewalls and management appliances together can easily leave a firewall on 7.4.12 and consider the job done.

Third, the fixed builds have been out since October 22.

Date (US time)EventBasis
October 21, 2026Fortinet chief information security officer Carl Windsor announces a "security hardening release" on the company blog. FortiMail and FortiAuthenticator builds ship the same dayFortinet blog
October 22FortiOS 8.0.2, 7.6.8, 7.4.13 and 7.2.14 ship, along with FortiManager and FortiAnalyzer buildsVersion table in the Fortinet blog
October 26Help Net Security reports that Fortinet is withholding details of the fixes until November 10Help Net Security
November 1089 advisories published. CVE-2026-126253 is FG-IR-26-267FortiGuard PSIRT
November 13Fortinet adds virtual-patch information to the BGP advisory (FG-IR-26-268). Rwanda NCSA issues its alertFortiGuard PSIRT, Rwanda NCSA

October 22 to November 10 is 19 days. An organization that upgraded FortiOS in a routine maintenance window during that period was already clear of this flaw before the advisory existed. One that deferred "an update that doesn't say what it fixes" met November 10 with the description and the fix public at the same moment. Windsor wrote in the October post that once updates are public, the fixes themselves reveal where changes were made. That is the stated reason for the gap between build and advisory.

2. What breaks — forged routes without a login, but only where OSPF is running

OSPF is the protocol routers and firewalls use to tell each other which networks lie in which direction and to choose paths accordingly. One unit of that information is a link-state advertisement, or LSA. Devices build their routing tables from the LSAs their neighbors send, which is why OSPF has an authentication step to check that a neighbor is genuine.

CVE-2026-126253 is a way around that check. Fortinet's advisory describes an "authentication bypass by primary weakness" (CWE-305) in the OSPF daemon of FortiOS and FortiSASE, through which an unauthenticated attacker may broadcast LSAs using a crafted request.

ItemDetailWhat it means
AdvisoryFG-IR-26-267Published November 10, 2026; no revisions since
TypeAuthentication bypass (CWE-305)The lock exists but there is a way around it
LocationOSPF daemonNo OSPF, no path
CVSS 3 score9.3 (Critical)Fortinet's own rating
Attack vectorAdjacent network (AV:A)The attacker must be on the same network segment; not directly reachable across the internet
PrivilegesNone (PR:N)No account, no password
ScopeChanged (S:C)The effect spreads beyond the one device attacked
ImpactConfidentiality none, integrity high, availability highIt does not read data directly; it changes or cuts routes
ExploitationMarked "No" in the advisoryAs of publication on November 10
DiscoveryInternalLoic Pantano of Fortinet's product security team, using the AI model Claude Mythos

The changed scope is what drives the 9.3. An LSA is information a device passes on to its own neighbors. If one device accepts a forged LSA, the other routers in the same OSPF area learn that route too. nFlo notes that injected LSAs can redirect or block traffic; traffic steered through a segment the attacker watches could become the starting point for a further attack. The impact the advisory itself states goes no further than improper access control, and no concrete attack scenario has been published.

Two conditions pull in the other direction.

ConditionIf yesIf no
Does the device run OSPF?It is in scopeThis path is closed. The same builds fix other flaws, so the upgrade is still needed
Can an attacker get onto a segment where OSPF runs?Attack is possible without a loginNot directly reachable from outside; still open to an attacker already inside

Rescana points out that Fortinet does not describe a remote internet path, and Panelica classes the flaw as configuration-dependent, behind five findings in the batch that are reachable unconditionally. A small office with a single firewall and static routes probably has OSPF off. An organization that ties headquarters, data centers and branches together with dynamic routing on its firewalls, or a carrier or plant network where the firewall doubles as a router, is squarely in scope.

And 9.3 is not the top score in this batch. Within FortiOS alone, CVE-2026-126254 in the BGP daemon is rated 9.6, and FortiMail, FortiManager and FortiAnalyzer carry 9.8s (section 4). A score describes how bad the worst case is, not whether the worst case holds in a given environment; our CVSS explainer goes through how the number is built.

3. What to do — check the version, follow the upgrade path, reduce exposure where an upgrade must wait

The order is: establish whether a device is in scope, upgrade, then reduce exposure on anything that cannot be upgraded yet.

StepTaskHowWhat to look for
1Check the versionThe Version line of get system status in the CLI, or the firmware field on the dashboard8.0.2, 7.6.8, 7.4.13 or 7.2.14 and later closes this flaw
2Check whether OSPF is in useshow router ospf for configuration, get router info ospf neighbor for neighborsEmpty configuration and no neighbors means this path does not apply
3Build the inventoryEvery FortiGate at headquarters, branches and in the cloud, including units run by integrators or managed service providersOne table with branch, version and OSPF use per device
4Back up the configurationDownload the configuration file before upgradingRecommended in Fortinet's October post
5Check the upgrade pathEnter current and target versions in Fortinet's upgrade path tool (docs.fortinet.com/upgrade-tool)Do not skip intermediate versions
6UpgradeOSPF devices first; every member of a high-availability pairRerun the step 1 command afterward
7VerifyNeighbors show FULL in get router info ospf neighbor; nothing unfamiliar in get router info ospf database briefCompare the routing table with the one from before the upgrade

Step 5 matters because FortiOS defines the intermediate versions a device must pass through when it crosses branches. Moving from 7.0 to 7.2.14, or from 7.2 to 7.4.13, triggers configuration conversion, so the sequence the tool gives should be followed. Penligent makes the same point: use the supported upgrade path and do not skip steps.

Devices that cannot be upgraded right away are the hard part. Fortinet's advisory offers no workaround for this flaw and lists no virtual patch. The measures below come from the InfoSec Monkey blog, Red Tiger Security and nFlo. They are not mitigations confirmed by Fortinet, and InfoSec Monkey itself says such countermeasures reduce exposure and are not fixes.

MeasureWhat it doesWhereLimit
Passive interfacesStops OSPF packets on interfaces with no real OSPF neighborset passive-interface under config router ospfInterfaces with real neighbors stay open
Known neighbors onlyAccepts OSPF (IP protocol 89) to the device only from known neighbor addressesAllow and deny rules in config firewall local-in-policyUntested against an attacker on the same segment spoofing a neighbor address
Route filterInstalls only expected prefixes learned from OSPF; rejects a default route (0.0.0.0/0)config router access-list with set distribute-list-inA forged route inside the permitted ranges passes
Segment reviewConfirms OSPF is not enabled on user, guest or internet-facing interfacesget router info ospf interfaceFinds configuration mistakes
MonitoringRecords unexpected changes in the routing table and LSA databaseQuery and compare on a scheduleDetection after the fact

One caution. InfoSec Monkey warns not to rely on OSPF MD5 authentication alone, since the flaw is precisely a bypass of authentication; keep authentication on and add the controls above. Local-in policies and route filters can also break adjacency with legitimate neighbors if entered wrongly and destabilize the whole network. Apply them in a maintenance window while watching that neighbors stay in FULL state.

FortiSASE needs little separate attention. According to the advisory, 26.3.1 and 26.3.1_a were remediated by Fortinet in 26.3.2 and customers need do nothing. Branches 25.1 through 26.2 are listed as affected in all versions with the instruction to migrate to a fixed release.

4. The other critical flaws published the same day — the 9.8s are in FortiMail and the management appliances

SecurityWeek reported that Fortinet's 89 advisories of November 10 cover nearly 100 vulnerabilities, about 17 of them critical and nearly 80 high. The SANS Internet Storm Center gave the same 89 and 17 in its November 12 Stormcast and noted that FortiMail received the most critical fixes. SecurityWeek's ranking of products with critical fixes runs FortiMail, FortiAuthenticator, FortiOS, FortiManager, FortiAnalyzer.

Scores below are Fortinet's. Fixed versions are given only where the advisory was opened directly or two or more sources agree.

ProductCVE (advisory)ScoreWhat it isConditionFixed in
FortiMailCVE-2026-126147 (FG-IR-26-199)9.8Path traversal; code or command execution without a loginNone8.0.2, 7.6.7, 7.4.9; 7.2 must migrate
FortiMailCVE-2026-126148 (FG-IR-26-200)9.8Command injection through HA join-request packets8.0 and 7.6 branches only8.0.2, 7.6.7
FortiMailCVE-2026-126164 (FG-IR-26-216)9.4SQL injectionNone8.0.2, 7.6.7, 7.4.9
FortiMailCVE-2026-126155, CVE-2026-1261569.1Session or account takeover of encrypted-mail (IBE) recipientsIBE in use8.0.2, 7.6.7, 7.4.9
FortiManager, FortiAnalyzerCVE-2026-126170 (FG-IR-26-219)9.8JSON injection in the JSON-RPC API; code or command execution without a loginJSON API enabled (off by default); 7.4 and 7.2 not affected8.0.3, 7.6.8, or the workaround
FortiManagerCVE-2026-126261 (FG-IR-26-275)9.0Elevation in the device-registration channel (FGFM) before the registration password is verifiedReach to the FGFM port (TCP 541)8.0.1, 7.6.8, 7.4.6, 7.2.9
FortiManager, FortiAnalyzerCVE-2026-126229 (FG-IR-26-244)9.1An administrator reaches virtual domains (VDOMs) outside their permissionsAuthenticated administrator8.0.2, 7.6.8, 7.4.12; 7.2 must migrate
FortiAnalyzer, FortiManagerCVE-2026-126262 (FG-IR-26-276), CVE-2026-126260 (FG-IR-26-274)9.3, 9.0SQL injection and server-side request forgery in the log channel (OFTP)Reach to the OFTP port (TCP 514)Check the advisory
FortiOS, FortiSASECVE-2026-126254 (FG-IR-26-268)9.6Numeric truncation in the BGP daemon; malformed attributes pushed to all connected routersMust be a configured iBGP neighbor (authenticated)8.0.2, 7.6.8, 7.4.13, 7.2.14
FortiOSCVE-2026-126259 (FG-IR-26-273)9.0Super-admin command execution through HA packetsOnly with FGSP plus standalone-config-sync, or autoscale8.0.1, 7.6.8, 7.4.13, 7.2.14; 7.0 must migrate
FortiAuthenticatorCVE-2026-126251, CVE-2026-1262579.1, 9.0Incorrect authorization; hard-coded passwordHigh attack complexity for the second8.0.4, 6.6.11

Three things stand out.

Unconditional reach comes first. CVE-2026-126147 in FortiMail needs no login and no particular configuration, and a mail appliance faces the internet by design. For an organization that does not run OSPF, FortiMail's 9.8 is far more urgent than FortiOS's 9.3. Fortinet's advisory says FortiMail Cloud was remediated on October 5, 2026 and its customers need not act.

FortiManager 8.0.2 leaves one flaw open. The FortiManager and FortiAnalyzer 8.0.2 builds from the October 22 hardening release fix most of the batch, but the advisory for the JSON-RPC flaw (CVE-2026-126170) lists 8.0.0 through 8.0.2 as affected and 8.0.3 as the fix. SecurityOnline and GBHackers report 8.0.3 as marked forthcoming. Until it ships, 8.0-branch management appliances depend on the advisory's workaround: set the JSON API permission (rpc-permit) to none on administrator profiles. Fortinet says the API is disabled by default.

Management ports do not belong on the internet. FGFM (TCP 541) and OFTP (TCP 514) are the channels firewalls use to register with a management appliance and send it logs. GBHackers notes that protecting the browser login page does nothing for these services. One FortiManager pushes policy to hundreds of firewalls, so a compromise there reaches everything below it.

The batch also includes a flaw in the FortiClient endpoint software. SecurityWeek reports a bug nicknamed "Fortinet2Shell" (CVE-2026-121529) by Kevin Joensen of Baldur Security, which he says lets an attacker run code when a user with FortiPAM enabled visits a malicious site. This rests on a single report.

5. Exploitation status, and why Fortinet keeps being targeted

The current state first.

CheckedResultAs of
"Known Exploited" field in Fortinet's advisories"No" in all six advisories opened directlyNovember 10 publication; November 13 revision for the BGP advisory
CISA Known Exploited Vulnerabilities catalogNone of the batch is listedCatalog version 2026.11.13, 1,781 entries
SecurityWeekFortinet makes no mention of exploitationNovember 11
Indicators of compromiseNone publishedRescana, checked November 11

"Not exploited yet" is a dated judgment. Penligent observes that the field is no proof that a particular deployment was never targeted. For Fortinet equipment the statement has had a short shelf life more than once.

FlawWhat it wasPublishedAdded to CISA KEVCourse
CVE-2022-40684 (FG-IR-22-377)Authentication bypass in the administrative interface of FortiOS, FortiProxy and FortiSwitchManager, 9.8October 10, 2022October 11, 2022Fortinet's advisory says it was aware of exploitation. KEV marks it as used in ransomware campaigns
CVE-2024-21762 (FG-IR-24-015)Out-of-bounds write in the FortiOS SSL VPN daemon, 9.8February 8, 2024February 9, 2024The advisory said it was potentially being exploited; KEV listing followed a day later with a seven-day federal deadline
CVE-2024-47575 (FG-IR-24-423)Missing authentication in the FortiManager registration daemon (fgfmd), 9.8October 23, 2024October 23, 2024Already exploited at disclosure; the advisory says so explicitly

In all three, publication and KEV listing were at most a day apart. The 2024 FortiManager flaw sat in the same channel, FGFM, as CVE-2026-126261 in the current batch, which is why Red Tiger Security sets the two side by side.

The November 13 KEV version holds 32 Fortinet entries. The most recent are CVE-2025-61624, a path traversal in FortiOS and other products added on October 16, 2026, and CVE-2026-104286, a path traversal in FortiMail added on October 1, 2026. Both carried three-day deadlines for US federal civilian agencies; the deadlines bind only those agencies, but they are a useful signal of urgency for anyone. In other words, a FortiMail path traversal was being exploited six weeks before November 10, the day another FortiMail path traversal, CVE-2026-126147, was published at 9.8.

Why Fortinet? The answer lies in where its products sit.

ReasonExplanation
They stand at the entranceFirewalls, VPN gateways and mail gateways sit between the internet and the internal network. Take one and you can see what is behind it
The management appliance is a leverOne FortiManager pushes policy to hundreds of firewalls
Monitoring tools are hard to install on themUnlike a general-purpose server, an appliance rarely runs endpoint detection software, so compromise is noticed late
Patching is slowA firewall upgrade interrupts the network and waits for a maintenance window
The patch becomes a mapOnce a fix ships, attackers compare builds to work back to the flaw

The last row explains the shape of this release. In the October 21 post Fortinet said some of the vulnerabilities were found through its use of frontier AI models in product security testing, and thanked Anthropic, OpenAI, Google and SpaceX for their collaboration. Windsor wrote that the window between disclosure and exploitation keeps shrinking and that the company expects it to keep shrinking. Fortinet also warned that AI can link seemingly unrelated lower-severity vulnerabilities into something more severe. Hence the sequence: ship the fix, give customers time to upgrade, publish the details 19 days later.

Five of the six advisories opened for this article credit a named Fortinet product security researcher together with Claude Mythos; the sixth, for the JSON-RPC flaw, credits an AI model without naming it. Magica cautions that Fortinet has not said how many of the roughly 100 vulnerabilities AI found, and that an "internal discovery" label does not by itself establish AI involvement. This is a case of a defender finding and fixing first with AI, but Fortinet's own premise is that the same capability shortens the time an attacker needs to read a patch. For a recent measurement of that interval, our piece on the Barracuda ESG flaws documents a one-week gap between patch and confirmed exploitation.

6. What remains open and what could not be confirmed

ItemConfirmedNot confirmed
Fixed versionsFortiOS 8.0.2, 7.6.8, 7.4.13, 7.2.14 (advisory and multiple sources agree)The 7.0.18 listed by Rwanda NCSA is not in the advisory
Attack methodOne sentence: a crafted request broadcasts LSAsThe form of the request, differences by OSPF authentication type, whether exploit code exists
Exploitation"No" per Fortinet; absent from the November 13 KEV versionAny change since; whether anyone analyzed the builds after October 22
WorkaroundNone in the advisoryWhether passive interfaces and local-in policies actually stop the attack
Size of the release89 advisories, nearly 100 vulnerabilities, about 17 critical (as reported)Totals stated by Fortinet itself; a definitive list of the 17
FortiManager 8.0.3Named in the advisory as the fix for the JSON-RPC flawIts release date
AI's shareSeveral advisories credit Claude MythosHow many of the roughly 100 AI found
Belgium's CCB alertTitle and address onlyThe page refused access and was not read
South Korea—Number of affected devices in the country; any separate advisory from Korean authorities

The order, then: FortiMail first if you run it; management appliances first if ports 541 or 514 face the internet; then FortiGates running OSPF or BGP, to 8.0.2, 7.6.8, 7.4.13 or 7.2.14. For 7.0, plan the branch migration. Conditions set the order, not the score.

Microsoft's side of the same month is in our "November 2026 Patch Tuesday — why a 6.5-rated Outlook zero-day, CVE-2026-124194, comes first among 1,094 fixes"; its conclusion, that exploitation and exposure outrank the score, applies equally to a 9.3-rated OSPF flaw. A recent case of a mail security appliance under attack is in "Barracuda ESG vulnerabilities patch versions"; handling a branch that gets no fix is covered in "What end of life (EOL) means"; and reading scores is covered in "What CVSS is".

Sources

  1. FortiGuard PSIRT — FG-IR-26-267 Authentication bypass by primary weakness (CVE-2026-126253, 2026-11-10)
  2. FortiGuard PSIRT — FG-IR-26-268 Numeric truncation error (CVE-2026-126254, 2026-11-10, updated 11-13)
  3. FortiGuard PSIRT — FG-IR-26-273 Unauthenticated adjacent command execution via HA (CVE-2026-126259, 2026-11-10)
  4. FortiGuard PSIRT — FG-IR-26-199 FortiMail path traversal (CVE-2026-126147, 2026-11-10)
  5. FortiGuard PSIRT — FG-IR-26-219 JSON Injection in JRPC API (CVE-2026-126170, 2026-11-10)
  6. FortiGuard PSIRT — FG-IR-26-275 FGFM elevation before registration password is verified (CVE-2026-126261, 2026-11-10)
  7. FortiGuard PSIRT — advisory index
  8. Fortinet blog — Fortinet Releases Security Hardening Release for Multiple Products (Carl Windsor, 2026-10-21, updated 11-10)
  9. CISA — Known Exploited Vulnerabilities Catalog JSON (catalog version 2026.11.13)
  10. SecurityWeek — Fortinet Patches Nearly 100 Vulnerabilities (2026-11-11)
  11. SANS Internet Storm Center — Stormcast 10176 (2026-11-12)
  12. Rwanda NCSA — Security Alert: Fortinet Security Updates, November 2026 (2026-11-13)
  13. Red Tiger Security — Fortinet November 2026: Critical FortiOS Routing Flaw and FortiManager Console Fixes
  14. Rescana — Fortinet November 2026 PSIRT: FortiMail and FortiManager Unauthenticated RCE (2026-11-11)
  15. InfoSec Monkey — Fortinet PSIRT Countermeasures for Pre-Auth Bugs
  16. SecurityOnline — Fortinet Patches Eight Critical Flaws in FortiOS, FortiManager and FortiAnalyzer (2026-11-10)
  17. GBHackers — Critical Fortinet Vulnerabilities (2026-11-11)
  18. Panelica — Fortinet November 2026 Advisories: Which of the 17 CVEs to Patch First (2026-11-12)
  19. nFlo — CVE-2026-126253: Authentication Bypass in FortiOS (2026-11-12)
  20. Penligent — Fortinet November 2026: FortiOS and Manager Fixes
  21. Help Net Security — Fortinet patches critical FortiOS flaws found with AI help (2026-10-26)
  22. Magica — Fortinet discloses nearly 100 flaws after AI-assisted testing (2026-11-11)
  23. FortiGuard PSIRT — FG-IR-24-423 Missing authentication in fgfmsd (CVE-2024-47575, 2024-10-23)
  24. FortiGuard PSIRT — FG-IR-24-015 Out-of-bound Write in sslvpnd (CVE-2024-21762, 2024-02-08)
  25. FortiGuard PSIRT — FG-IR-22-377 Authentication bypass in administrative interface (CVE-2022-40684, 2022-10-10)

Verification

Published
Last modified
Cross-check
Checked against 25 independent sources.
Unverified
  • The alert page of the Centre for Cybersecurity Belgium (CCB) returned HTTP 403 and could not be opened; nothing in this article rests on it. Action1's November third-party patch digest could not be opened for the same reason.
  • The totals — 89 advisories, nearly 100 vulnerabilities, about 17 critical, nearly 80 high — come from SecurityWeek, the SANS Stormcast and the Rwanda NCSA alert. No Fortinet statement giving the totals was found. SANS says more than 100 vulnerabilities while SecurityWeek and Rwanda NCSA say nearly 100. Lists of the 17 critical flaws differ by one or two entries between sources.
  • The Rwanda NCSA alert also lists FortiOS 7.0.18 or above as a fixed version. Fortinet advisory FG-IR-26-267 lists 7.0.1 through 7.0.19 as affected with no fix, only migration. This article follows the advisory.
  • The CVSS vector for CVE-2026-126253 (AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H) was read from the score link in the advisory. The advisory's temporal metrics show proof-of-concept exploit maturity (E:P); whether public exploit code exists was not confirmed.
  • FG-IR-26-267 contains no workaround. The interim measures in section 3 (passive interfaces, local-in policies limiting IP protocol 89, route filters) are exposure-reduction steps proposed by the InfoSec Monkey blog, Red Tiger Security and nFlo, not mitigations confirmed by Fortinet. No source demonstrates that they stop the attack.
  • Of the CLI commands in section 3, the OSPF neighbor and database queries were confirmed in the InfoSec Monkey post. The version and OSPF configuration commands are general FortiOS commands, not taken from the advisory. Menu names vary by FortiOS release.
  • Fortinet scores CVE-2026-126259 at 9.0 while SecurityOnline and Panelica give 9.8; CVE-2026-126261 is likewise 9.0 from Fortinet and 9.8 in some reports. Rescana says the US National Vulnerability Database shows 9.8 for the same vector. The tables here use Fortinet's scores.
  • Among the FortiMail critical flaws, CVE-2026-126147 was confirmed in the advisory itself. Scores and versions for CVE-2026-126148, 126164, 126155 and 126156 were confirmed through Rescana's advisory review and Panelica's list; those advisories were not opened. CVE-2026-126263, 126150 and 126157, listed as FortiMail critical flaws only by Panelica, are left out of the table.
  • Fixed versions for the FortiAnalyzer OFTP flaws (CVE-2026-126262, CVE-2026-126260) appeared in only one source, InfoSec Monkey, and are not given. The FortiAuthenticator fixes 8.0.4 and 6.6.11 (CVE-2026-126251, CVE-2026-126257) were confirmed in Fortinet's blog version table and Rescana; the advisories were not opened.
  • The FortiClient flaw nicknamed Fortinet2Shell (CVE-2026-121529) was confirmed only in SecurityWeek.
  • Fortinet has not said how many of the roughly 100 vulnerabilities were found with AI models. The Claude Mythos credit was confirmed in five advisories opened directly (FG-IR-26-267, 268, 273, 199, 275). FG-IR-26-219 credits an AI model without naming it.
  • The nickname FortiJump for the 2024 FortiManager flaw CVE-2024-47575 follows Red Tiger Security's usage; Fortinet's advisory does not use it.
  • No count of affected devices in South Korea, and no separate advisory from Korean authorities, was found in this reporting.
Authoring
Reviewed by a person before publication. The full process is described in the Editorial.

Ten stories, once each morning

We send the three-line summaries only; the full pieces stay on the site. One-click unsubscribe, any time.

Related