
Offline version-triage CLI that grades FortiOS, FortiManager, FortiAnalyzer and FortiSASE builds against eight Fortinet PSIRT CVEs, reporting per-CVE status and exposure without probing appliances.
fortinet-scannerLocal triage for the Fortinet November 2026 PSIRT batch, eight Critical flaws (CVSS 9.0 to 9.8) across FortiOS, FortiManager, FortiAnalyzer and FortiSASE, published 10 November 2026. Give it a product and a version you own, from get system status or the GUI, and it tells you which of the eight still apply to that box. It never sends a packet, never probes an appliance, never attempts a login.
The flawsOn 10 November 2026 Fortinet published 89 advisories covering close to 100 vulnerabilities, found with AI-assisted testing (Fortinet credits the frontier model Claude Mythos in the acknowledgements). The patches themselves shipped in the October hardening release, so the details landing on 10 November is what opened the window, and Fortinet warns attackers can now diff a patch and have a working exploit within hours or days. None of the eight is listed as known exploited, and none was in CISA's KEV catalog as of 11 November 2026.
CVE-2026-126170 (FG-IR-26-219, 9.8, CWE-116): improper encoding in the FortiManager / FortiAnalyzer JSON-RPC API. An unauthenticated attacker may run code or commands through a crafted HTTP request, but only when the JSON API is enabled on an admin profile. It is disabled by default.CVE-2026-126254 (FG-IR-26-268, 9.6, CWE-197): numeric truncation in the FortiOS / FortiSASE BGP daemon. A configured iBGP neighbour may send malformed attributes to all connected routers. Authenticated, not unauthenticated, despite the 9.6.CVE-2026-126253 (FG-IR-26-267, 9.3, CWE-305): authentication bypass in the FortiOS / FortiSASE OSPF daemon. An unauthenticated attacker on an adjacent network may broadcast forged link state advertisements.CVE-2026-126262 (FG-IR-26-276, 9.3, CWE-89): SQL injection in the OFTP log-reception service (TCP/514) of FortiAnalyzer, and of FortiManager with FortiAnalyzer features enabled. Unauthenticated, may run code or commands.CVE-2026-126229 (FG-IR-26-244, 9.1, CWE-639): authorization bypass through a user-controlled key in dmserver. An authenticated administrator may reach other VDOMs through crafted HTTP requests.CVE-2026-126261 (FG-IR-26-275, 9.0, CWE-285): improper authorization in the FortiManager FGFM service (TCP/541). An unauthenticated attacker who can reach the FGFM port may run code or commands, because the check happens before the registration password is verified.CVE-2026-126260 (FG-IR-26-274, 9.0, CWE-918): pre-authentication SSRF in the same OFTP service as CVE-2026-126262.CVE-2026-126259 (FG-IR-26-273, 9.0, CWE-306): missing authentication in FortiOS high availability. An unauthenticated attacker may run commands as super admin through crafted HA packets, but only on clusters using FGSP with standalone-config-sync, or autoscale.The trapsSignal | Grade | Why |
|---|---|---|
FortiManager 8.0.1 | PATCHED for CVE-2026-126261, VULNERABLE for CVE-2026-126170 and CVE-2026-126229 | The one-build-does-not-clear-the-batch trap. 8.0.1 meets the FGFM threshold while still falling in the affected range for the JSON-RPC, OFTP and dmserver flaws. Each CVE has its own fix table, and this tool grades all eight separately. |
FortiManager / FortiAnalyzer 8.0.2 | VULNERABLE for CVE-2026-126170 | The October-fix-level trap. 8.0.2 is the October hardening build and it is still affected. The fix is the upcoming 8.0.3; until it ships, the workaround is set rpc-permit none on the admin profile. |
FortiOS 7.0 | VULNERABLE, no fix | The no-fix branch trap. 7.0 has no fix for the OSPF and HA flaws (and for dmserver on FM/FA) and must migrate to a fixed release. |
FortiAnalyzer 8.0.1 | VULNERABLE for CVE-2026-126262, PATCHED for CVE-2026-126260 | The OFTP split trap. The SSRF advisory fixes 8.0.1, the SQLi advisory needs 8.0.2 on FortiAnalyzer. FortiManager needs only 8.0.1 for both. Do not copy one product's fix onto the other. |
FortiOS 7.0 for CVE-2026-126254 | UNKNOWN | The missing-row trap. The BGP advisory lists no 7.0 row at all, while the OSPF advisory lists 7.0.1 to 7.0.19 as migrate. This tool does not infer 7.0 status for the BGP flaw from the OSPF advisory. |
FortiManager / FortiAnalyzer 7.4 or 7.2 for CVE-2026-126170 | NOT-AFFECTED | The wrong-branch trap. The JSON-RPC flaw touches only the 8.0 and 7.6 lines. A 7.4 manager needs no upgrade for this CVE, even though the same box may be open to the OFTP and dmserver flaws. |
FortiSASE 26.3.1 / 26.3.1_a | VULNERABLE, fix 26.3.2 | Fortinet remediated the routing flaws in 26.3.2 with no customer action needed, but 26.3.1 is still open. 26.2 and earlier 25.x must migrate; 22.4 to 24.4 are not affected. |
FortiSASE-Sovereign 26.2 | PATCHED | Remediated before release, no action needed. 25.x must migrate. Do not mix FortiSASE and FortiSASE-Sovereign tables: they are different products with different fixes. |
Cloud versions for the OFTP pair | UNKNOWN | The OFTP advisories list no Cloud rows, so a Cloud version is left ungraded for CVE-2026-126262 and CVE-2026-126260, not cleared. |
What it checksOne box (--product fortios --version 7.4.13): graded against all eight CVEs, per productA get system status line (--product fortimanager --version "Version: FortiManager v8.0.1,build..."): parsed, suffixes like 26.3.1_a handledExposure, per flaw (--no-json-api, --no-ospf, --no-ibgp, --no-ha-fgsp, --no-fgfm, --no-oftp, --single-vdom, --no-fa-features): a version in range with the prerequisite off grades NOT-EXPOSED, not VULNERABLE. Unknown exposure is assumed exposed, and the note says soA version file (--version-file version.txt): first line is the version, which may be a full get system status lineA fleet, offline (--inventory-json fleet.json): a JSON list of {label, product, version} entries, with optional exposure booleans per boxThe full table (--list): affected ranges and fixed releases for all eight CVEsMachine output (--json): the same grades as JSONpython3 fortinet_scanner.py --product fortios --version 7.4.13
python3 fortinet_scanner.py --product fortimanager --version 8.0.1
python3 fortinet_scanner.py --product fortios --version 7.4.12 --no-ospf --no-ibgp
python3 fortinet_scanner.py --product fortimanager --version 8.0.1 --no-json-api
python3 fortinet_scanner.py --product fortianalyzer --version-file version.txt
python3 fortinet_scanner.py --inventory-json fleet.json
[
{"label": "gate-01", "product": "fortios", "version": "7.4.12"},
{"label": "mgr-01", "product": "fortimanager", "version": "8.0.1"},
{"label": "anlz-01", "product": "fortianalyzer", "version": "8.0.1", "oftp": true}
]
Exit codes: 0 nothing vulnerable found, 2 vulnerable finding, 1 scan error. UNKNOWN does not change the exit code, but it is not clean.
Find your version with get system status on the appliance CLI, or from the GUI (System > Firmware on a FortiGate, System Settings > Dashboard on FortiManager / FortiAnalyzer). Paste the version string, not a screenshot.
The table