Fortinet November 2026 PSIRT: Five Critical Fix Paths to Check Now

Five Fortinet advisories published November 10 carry critical CVSSv3 scores and different exposure conditions. Check the exact predicate, fixed branch, availability caveats, and bounded mitigation guidance for each path.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Reader ratings require JavaScript; the article remains fully readable without it.

November disclosure update

Decision: Fortinet’s November 10 advisories turn the October hardening notice into five configuration-specific patch decisions. Match each device to the exact exposure predicate below before treating it as affected, then use the branch-specific fixed release or the vendor’s stated workaround or mitigation.[1][2][3][4][5]

Reporting cutoff: November 11, 2026 at 3:30 p.m. EST (20:30 UTC). The five live Fortinet advisory pages, their first-party CSAF records, NVD responses, and CISA’s KEV feed were re-fetched for this update.

5 advisoriesFortinet published FG-IR-26-219, -267, -268, -273, and -275 on November 10, each with a distinct prerequisite.[1][2][3][4][5]
CVSS 9.0–9.8The five Fortinet pages display CVSSv3 scores of 9.8, 9.3, 9.6, 9.0, and 9.0.[1][2][3][4][5]
Known exploited: “No”Every Fortinet page displayed “Known Exploited: No” at the cutoff.[1][2][3][4][5] That is Fortinet’s current statement, not proof that exploitation has never occurred.

Five different exposure predicates

A vulnerable version alone does not make all five flaws reachable. The relevant predicates are: JSON API enabled; OSPF traffic reaching the daemon; a configured iBGP neighbor; HA FGSP plus standalone-config-sync or autoscale; and network reachability to the FortiManager FGFM port.[1][2][3][4][5]

Advisory / CVE Exposure predicate Fortinet score and fixed branches
FG-IR-26-219
CVE-2026-126170
The JRPC issue exists only when the JSON API is enabled; Fortinet says it is disabled by default. 9.8. FortiAnalyzer, FortiAnalyzer Cloud, FortiManager, and FortiManager Cloud: 8.0.3 is upcoming; 7.6 fixes at 7.6.8. FortiAnalyzer BigData: 7.6.3 is upcoming. FortiSASE-Sovereign 26.2 was remediated before release; listed 25.x branches must migrate to a fixed release. The workaround is available while the named builds are unavailable.[1]
FG-IR-26-267
CVE-2026-126253
An unauthenticated attacker must be able to send a crafted request to the OSPF daemon; Fortinet describes broadcast of LSA. 9.3. FortiOS fixes: 8.0.2, 7.6.8, 7.4.13, and 7.2.14 or later. FortiSASE 26.3.1/26.3.1_a was remediated in 26.3.2; affected earlier service branches must migrate to a fixed release.[2]
FG-IR-26-268
CVE-2026-126254
The sender must be a configured iBGP neighbor. Fortinet classifies the attack as authenticated; its vector includes PR:L. 9.6. FortiOS fixes: 8.0.2, 7.6.8, 7.4.13, and 7.2.14 or later. FortiSASE service-branch guidance matches the OSPF advisory.[3]
FG-IR-26-273
CVE-2026-126259
Exposure requires HA FGSP with standalone-config-sync, or autoscale; Fortinet describes crafted HA packets. 9.0. FortiOS fixes: 8.0.1, 7.6.8, 7.4.13, and 7.2.14 or later. The live page presents those targets as upgrades, while Fortinet’s CSAF labels the 7.6.8, 7.4.13, and 7.2.14 builds “upcoming.” A virtual patch named FG-VD-61445.0day. is listed in FMWP database update 26.082.[4]
FG-IR-26-275
CVE-2026-126261
An unauthenticated attacker must be able to reach the FortiManager FGFM port and send crafted FGFM packets. 9.0. FortiManager fixes: 8.0.1, 7.6.8, 7.4.6, and 7.2.9 or later.[5]

Score caveat: The Fortinet pages label the five values as “CVSSv3 Score.” First-party CSAF records separately type those values as baseScore; their vectors also contain temporal metrics such as E, RL, and RC, and FG-IR-26-219 separately records a temporalScore of 8.9. Keep the displayed scores, typed base scores, temporal score, and temporal vector metrics distinct.[1][5]

What to do now

  1. Practical guidance — inventory the exact branch and predicate. As a bounded operational inference from the five advisory predicates, record product, running build, role, and whether the matching JSON API, OSPF, configured iBGP, HA/autoscale, or FGFM condition exists. Do not combine the predicates or assume a device affected by one advisory is exposed to all five.[1][2][3][4][5]
  2. For CVE-2026-126170, disable the JSON API where it is not required. Fortinet’s workaround is to edit the affected administrator profile and set rpc-permit none. Treat this as a scoped workaround for FG-IR-26-219, not a fix for the other four advisories.[1]
  3. Use Fortinet’s supported upgrade path. Apply the exact branch target above only after checking the vendor Upgrade Path Tool and release process; do not jump branches from this summary alone.[2][3][4]
  4. Do not treat an “upcoming” build as downloadable. For FG-IR-26-219, use the stated workaround until the applicable build is actually available. For FG-IR-26-273, confirm availability because the live page and CSAF disagree on the three older branch targets.[1][4]
  5. Practical guidance — treat the listed virtual patch as an interim control. Fortinet lists FG-VD-61445.0day. in FMWP database 26.082 for FG-IR-26-273. As a bounded operational inference, confirm applicability in your deployment and keep the vendor’s software upgrade path as the remediation target; this package does not claim the signature is present or enforced.[4]
  6. Back up and monitor around the change. Fortinet’s October hardening guidance says to save current configurations and watch logs for unusual administrative access or unapproved configuration changes before and after patching.[8]

Practical guidance: Validate the running version on every cluster member after maintenance and preserve your change and rollback records.[8] This is bounded defensive operating advice; it is not a claim that any device was compromised.

What “no known exploitation” does—and does not—mean

At the cutoff, all five Fortinet advisories said “Known Exploited: No.”[1][2][3][4][5] That supports only the vendor’s point-in-time status.

The NVD API returned zero records for CVE-2026-126170, -126253, -126254, and -126259, while CVE-2026-126261 appeared as a newly received vendor record.[6] CISA’s KEV feed was catalog version 2026.11.10, released before Fortinet’s late-November-10 disclosure records, so its silence cannot independently settle exploitation status for these CVEs.[7]

No victim count, incident report, or exploitation evidence appears in the reviewed Fortinet advisories. Absence from these bounded sources is not evidence that exploitation is impossible or has never happened.[1][2][3][4][5]

Open Fortinet’s PSIRT advisory index

Sources

  1. Fortinet FG-IR-26-219 — JSON Injection in JRPC API
  2. Fortinet FG-IR-26-267 — OSPF authentication bypass
  3. Fortinet FG-IR-26-268 — BGP numeric truncation error
  4. Fortinet FG-IR-26-273 — HA command execution
  5. Fortinet FG-IR-26-275 — FGFM authorization issue
  6. NVD — CVE-2026-126261 record (with frozen API checks for all five identifiers)
  7. CISA Known Exploited Vulnerabilities Catalog
  8. Fortinet — October coordinated hardening guidance