CVE-2026-126170: Unauthenticated Code Execution via JSON Injection in Fortinet JRPC API
- Vendor
- Fortinet
CVE-2026-126170 is an improper output encoding or escaping vulnerability in the JSON-RPC API of Fortinet FortiAnalyzer, FortiManager, and related deployments. When the JSON API is enabled, an unauthenticated attacker can send specially crafted HTTP requests that may trigger JSON injection and execute unauthorized code or commands. Affected versions include FortiAnalyzer and FortiManager 7.6.0–7.6.7 and 8.0.0–8.0.2; FortiAnalyzer Cloud and FortiManager Cloud 7.6.0–7.6.7 and 8.0.1–8.0.2; and FortiAnalyzer-BigData 7.6.0–7.6.2. FortiSASE-Sovereign is also affected. The JSON API is disabled by default. The vulnerability has a CVSS v3.0 base score of 9.8.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation may permit unauthenticated remote code or command execution on the affected system, compromising confidentiality, integrity, and availability. Denial of service is also identified as a potential impact. The execution privilege level is not specified.
Mitigation
If you can’t patch tonight, do this now.
Disable the JSON API on every administrative profile where it is enabled using: config system admin profile; edit <profile name>; set rpc-permit none; end. The API is disabled by default. Restrict network access to management services to trusted administrative systems as an additional exposure-reduction measure. No virtual patch is listed.
Remediation
Patch, then assume compromise.
Upgrade affected FortiAnalyzer, FortiAnalyzer Cloud, FortiManager, and FortiManager Cloud 7.6 installations to version 7.6.8 or later. Upgrade affected 8.0 installations to version 8.0.3 or later, and FortiAnalyzer-BigData 7.6 installations to version 7.6.3 or later. Fortinet advisory FG-IR-26-219 identifies 8.0.3 and FortiAnalyzer-BigData 7.6.3 as upcoming; verify availability and use the workaround until the applicable release is available. Migrate affected FortiSASE-Sovereign 25, 25.3, and 25.4 installations to a fixed release. For FortiSASE-Sovereign 26.2, Fortinet states that remediation occurred before release and no customer action is required, although its affected-version table conflicts with that statement; confirm applicability with Fortinet.
Exploits
3 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-126170 exploited in the wild?
- As of Nov 16, 2026, Mallory has no reports of CVE-2026-126170 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-126170?
- Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2026-126170, the earliest disclosed Nov 11, 2026.
- Is there a patch for CVE-2026-126170?
- Upgrade affected FortiAnalyzer, FortiAnalyzer Cloud, FortiManager, and FortiManager Cloud 7.6 installations to version 7.6.8 or later. Upgrade affected 8.0 installations to version 8.0.3 or later, and FortiAnalyzer-BigData 7.6 installations to version 7.6.3 or later.
- What products are affected by CVE-2026-126170?
- Fortinet Fortianalyzer, Fortinet Fortianalyzer-Bigdata, and Fortinet Fortimanager.
- How severe is CVE-2026-126170?
- CVE-2026-126170 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.63% (51st percentile) as of Nov 16, 2026.
Recent activity
21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.