If you turn on the API, someone without a login may run code or commands.Fortinet assigns CVSS 3.1 score 9.8, Critical. The company published FG-IR-26-219 on November 10, 2026.
What it allows
What Is the Impact of CVE-2026-126170?
Fortinet says the JSON API is off by default. Check if it is on. If it is, find the admin profiles that grant access. Check which networks can reach the API.
The advisory summary says someone may run code or commands. Its impact label says denial of service. Start with affected hosts that outside users can reach.
Is the Fortinet JSON API Flaw Known to Be Exploited?
Fortinet marked Known Exploited as No in FG-IR-26-219. CVE-2026-126170 was absent from CISA KEV catalog version 2026.11.10, released November 10, 2026.
See the Fortinet November advisory overview for related coverage. Use the vulnerability management guide to track upgrades and verify them after deployment.
This JSON API issue is one of three advisories compared in our Fortinet November critical-flaws patch-priority analysis.
Who is affected
Which Releases Are Affected by CVE-2026-126170?
Fortinet lists FortiManager and FortiAnalyzer appliances, their cloud editions, FortiAnalyzer-BigData, and FortiSASE-Sovereign. The upgrade path depends on both the product and release line.
| Product and release line | Affected releases | Fortinet solution |
|---|---|---|
| FortiAnalyzer 8.0 | 8.0.0 through 8.0.2 | Apply the workaround while 8.0.3 or later is pending |
| FortiAnalyzer 7.6 | 7.6.0 through 7.6.7 | Upgrade to 7.6.8 or above |
| FortiAnalyzer 7.4 | Not affected | Not Applicable |
| FortiAnalyzer 7.2 | Not affected | Not Applicable |
| FortiAnalyzer Cloud 8.0 | 8.0.1 through 8.0.2 | Apply the workaround while 8.0.3 or later is pending |
| FortiAnalyzer Cloud 7.6 | 7.6.0 through 7.6.7 | Upgrade to 7.6.8 or above |
| FortiAnalyzer Cloud 7.4 | Not affected | Not Applicable |
| FortiAnalyzer Cloud 7.2 | Not affected | Not Applicable |
| FortiAnalyzer-BigData 7.6 | 7.6.0 through 7.6.2 | Apply the workaround while 7.6.3 or later is pending |
| FortiAnalyzer-BigData 7.4 | Not affected | Not Applicable |
| FortiAnalyzer-BigData 7.2 | Not affected | Not Applicable |
| FortiManager 8.0 | 8.0.0 through 8.0.2 | Apply the workaround while 8.0.3 or later is pending |
| FortiManager 7.6 | 7.6.0 through 7.6.7 | Upgrade to 7.6.8 or above |
| FortiManager 7.4 | Not affected | Not Applicable |
| FortiManager 7.2 | Not affected | Not Applicable |
| FortiManager Cloud 8.0 | 8.0.1 through 8.0.2 | Apply the workaround while 8.0.3 or later is pending |
| FortiManager Cloud 7.6 | 7.6.0 through 7.6.7 | Upgrade to 7.6.8 or above |
| FortiManager Cloud 7.4 | Not affected | Not Applicable |
| FortiManager Cloud 7.2 | Not affected | Not Applicable |
| FortiSASE-Sovereign 26.2 | 26.2 all versions | Remediated in unreleased 26.2. Fortinet says customers need take no action. |
| FortiSASE-Sovereign 25.4 | 25.4 all versions | Migrate to a fixed release |
| FortiSASE-Sovereign 25.3 | 25.3 all versions | Migrate to a fixed release |
| FortiSASE-Sovereign 25 | 25 all versions | Migrate to a fixed release |
Fortinet lists two fixes as upcoming: 8.0.3 for affected 8.0 products and 7.6.3 for FortiAnalyzer-BigData. Check if your fix is out before you set a date to patch.
Until you can patch, Fortinet says to turn off JSON API access on admin profiles that use it. Fortinet lists no virtual patch.
Check FG-IR-26-219 before you patch. Match the full product name and release to the same row in the table. Note which hosts need a fix and which ones need the workaround. The patch management glossary describes the process of applying and verifying fixes.
Timeline
- 2026-11-10
Fortinet published FG-IR-26-219 and marked Known Exploited as No.
- 2026-11-11
The CVE Program and NVD published the CVE-2026-126170 records attributed to Fortinet.
What to do
-
Check JSON API access
Identify affected Fortinet deployments and check whether any administrator profiles enable JSON API access. Include appliances, cloud editions, and FortiAnalyzer-BigData in the inventory.
-
Apply the release-specific fix or workaround
Use the solution for the product and release line in FG-IR-26-219. If a fix is pending, disable JSON API access on admin profiles where enabled, following Fortinet’s guidance.
-
Verify the change
Confirm the installed firmware after an upgrade. If using the workaround, verify the admin profile configuration and check the advisory again for release availability.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-126170 in Brandefense Atlas
The Atlas record of CVE-2026-126170: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-126170 require a login?
Fortinet says unauthorized code or command execution can occur without authentication when JSON API access is enabled. The vendor says the API is disabled by default.
What can teams do while the vendor’s fix is pending?
Fortinet directs administrators to disable JSON API access on admin profiles where enabled. Recheck the advisory for the fixed release and plan the upgrade.
Does FortiSASE-Sovereign require a different action?
Yes. Fortinet says customers need take no action for the unreleased, remediated 26.2 line. It directs users on the 25.4, 25.3, and 25 lines to migrate to a fixed release.
Is CVE-2026-126170 listed as exploited?
Fortinet marked Known Exploited as No in FG-IR-26-219. CVE-2026-126170 was absent from CISA KEV catalog version 2026.11.10, released November 10, 2026.
Sources
- FG-IR-26-219 Fortinet security advisoryFortinet PSIRT
- CVE-2026-126170 Fortinet CNA recordCVE Program
- CVE-2026-126170National Vulnerability Database
- Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency