Automated Threat Modeling

Overview of CVE-2026-126170: Unauthenticated JSON Injection in the FortiManager and FortiAnalyzer JRPC API

A summary of CVE-2026-126170, a CWE-116 JSON injection in the JRPC API of FortiManager, FortiAnalyzer and related Cloud and BigData products. Fortinet rates it 9.8, and it is reachable only when JSON API access is enabled. Includes Fortinet's fixed releases, the rpc permission workaround, and an 8.0.2 caveat.

CVE Analysis

8 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Overview of CVE-2026-126170: Unauthenticated JSON Injection in the FortiManager and FortiAnalyzer JRPC API

Introduction

FortiManager and FortiAnalyzer sit at the center of many Fortinet deployments. One manages device configuration from a single console, and the other aggregates logs and security analytics. A flaw that may let an unauthenticated attacker execute code or commands on these systems through a crafted HTTP request deserves careful, configuration-aware triage. CVE-2026-126170 is that kind of flaw, and Fortinet has given it a CVSS 3.1 score of 9.8.

The most important qualifier is that the vulnerable code path is reachable only when JSON API access is enabled on an administrative profile, which Fortinet says is off by default. The 8.0 branch also has a version trap. 8.0.2, which shipped in Fortinet's October security hardening release, is still vulnerable to this CVE.

Technical information

Root cause: CWE-116 in the JRPC API

Fortinet tracks this issue in advisory FG-IR-26-219, titled JSON Injection in JRPC API, and assigns it to the GUI component. The weakness is classified as CWE-116, Improper Encoding or Escaping of Output. MITRE defines this class as preparing a structured message without appropriate encoding or escaping, so the intended structure is not preserved and attacker-supplied special characters can be interpreted as control information or metadata instead of data.

Fortinet has not published source code, diffs, or the exact vulnerable function. Based on the bug class and the patch notes we were given, the conceptual mechanism is as follows:

  • Data from an untrusted HTTP request is placed into a JSON structure that is then passed to a backend component behind the JSON RPC (JRPC) API.
  • Structural characters such as quotes, braces and backslashes are not properly escaped before that JSON is assembled.
  • An attacker can therefore break out of the intended field and add or override keys in the resulting message.
  • When those injected keys control backend operations, the result can be unauthenticated execution of code or commands.

The standard correction for this class of flaw is to build JSON with a proper serializer rather than by joining strings, and to escape or reject structural characters in untrusted fields before the message reaches the JRPC dispatcher. Treat this as an explanation of the bug class, not a description of Fortinet's implementation.

Attack prerequisites

The disclosed conditions are:

  1. The attacker can reach the affected product over the network (AV:N).
  2. No authentication or user interaction is required (PR:N, UI:N).
  3. JSON API access is enabled on at least one administrative profile. Fortinet states the vulnerability exists only when this API is enabled, and it is disabled by default.

An affected version number alone does not establish exposure. Assess the product, the version and the admin profile configuration together.

Conceptual attack flow

Based on the briefing, exploitation would proceed roughly like this:

  1. Identify a FortiManager or FortiAnalyzer instance (or a Cloud or BigData variant) running an affected build with JSON API access enabled.
  2. Send a specially crafted HTTP request to the JRPC API containing structural JSON characters in a field that the backend embeds without escaping.
  3. The injected characters terminate the intended value and introduce attacker-controlled keys into the JSON message forwarded to the backend.
  4. The backend acts on those keys, which may result in execution of unauthorized code or commands.

Severity scoring

Fortinet supplies the following base vector:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

This yields 9.8, Critical. NVD lists Fortinet as the scoring source and the record is in Received status, so this is the vendor assessment rather than a completed independent NIST assessment.

What has not been disclosed

The advisory does not disclose the HTTP endpoint, method, port, malicious parameters, payload, vulnerable function, the privilege level of any resulting execution, or a working exploit. The available sources do not support claims that execution occurs as root or administrator.

Exploitation status

Fortinet marks the issue Known Exploited: No. A Health ISAC bulletin dated November 11, 2026, which explicitly includes CVE-2026-126170, reports no active exploitation of the vulnerabilities it covers. No threat actor, campaign or indicators have been published. This reflects activity observed at disclosure time and is not a guarantee.

Disclosure timeline

  • 22 October 2026: FortiManager 7.6.8 build 3788 and FortiAnalyzer 7.6.8 build 3788 published as part of a coordinated security hardening release.
  • 10 November 2026: Fortinet publishes FG-IR-26-219.
  • 11 November 2026: NVD publishes the CVE record.

Fortinet credits Loic Pantano of its Product Security team, who found the issue internally with the help of a frontier AI model (the briefing names Claude Mythos). That fits the AI-assisted testing program behind the October hardening release.

Patch information

Fortinet published the fix through PSIRT advisory FG-IR-26-219. FortiManager and FortiAnalyzer are closed-source appliances, and no commit, diff or source-level patch notes have been released, so this section describes the fix in terms of firmware versions and the vendor workaround.

Fixed releases by branch

  • FortiManager 7.6 (7.6.0 through 7.6.7): upgrade to 7.6.8 or above (available).
  • FortiAnalyzer 7.6 (7.6.0 through 7.6.7): upgrade to 7.6.8 or above (available).
  • FortiManager Cloud 7.6 and FortiAnalyzer Cloud 7.6 (7.6.0 through 7.6.7): 7.6.8 or above.
  • FortiManager and FortiAnalyzer 8.0 (8.0.0 through 8.0.2): upcoming 8.0.3, or apply the workaround.
  • FortiManager Cloud and FortiAnalyzer Cloud 8.0 (8.0.1 through 8.0.2): upcoming 8.0.3, or apply the workaround.
  • FortiAnalyzer BigData 7.6 (7.6.0 through 7.6.2): upcoming 7.6.3, or apply the workaround.
  • FortiSASE Sovereign 25, 25.3 and 25.4 (all versions): migrate to a fixed release.
  • FortiSASE Sovereign 26.2: Fortinet fixed the issue before this release shipped, so no customer action is needed.
  • 7.4 and 7.2 branches of all listed products: not affected.

Builds available now

Fortinet's firmware feed lists FortiManager 7.6.8 build 3788 and FortiAnalyzer 7.6.8 build 3788, published on 22 October 2026 as part of a coordinated security hardening release roughly three weeks ahead of the advisory. Fortinet's CISO blog describes this sequencing as deliberate, meant to give customers time to upgrade before technical details were published. The same blog notes that once updates are public, attackers can diff the fixes to locate weak code. That matters here because 7.6.8 is public while the 8.0 branch has no fixed build yet.

Caveat: 8.0.2 does not cover this CVE

The hardening blog lists FortiManager and FortiAnalyzer 8.0.2 as the fixed version for that release. FG-IR-26-219, however, lists 8.0.0 through 8.0.2 as vulnerable to CVE-2026-126170, with the fix only in the unreleased 8.0.3. If you moved to 8.0.2 during the October cycle, you remain exposed to this CVE.

Release notes do not mention the CVE

The public Resolved issues page for FortiManager 7.6.8 lists functional bug fixes only and has no CVE line for this issue, which is consistent with shipping the fix before disclosure. Use the PSIRT advisory, not the release notes, to determine which builds contain the fix.

Workaround for branches without a fix

For 8.0.x and FortiAnalyzer BigData 7.6.x, Fortinet's interim measure is to remove RPC permission from every admin profile that has it:

config system admin profile edit <profile name> set rpc-permit none end

This does not repair the encoding flaw. It closes the JRPC entry point the attack depends on. Restore RPC permission only after moving to 8.0.3 or BigData 7.6.3. Fortinet lists Virtual Patch: No, so no IPS signature is available. Upgrading or applying the workaround are the only vendor-supported options.

Health ISAC also recommends identifying exposed Fortinet instances, prioritizing updates, applying official updates after appropriate testing, and validating system integrity.

Affected systems and versions

  • FortiAnalyzer 8.0.0 through 8.0.2
  • FortiAnalyzer 7.6.0 through 7.6.7
  • FortiAnalyzer Cloud 8.0.1 through 8.0.2
  • FortiAnalyzer Cloud 7.6.0 through 7.6.7
  • FortiAnalyzer BigData 7.6.0 through 7.6.2
  • FortiManager 8.0.0 through 8.0.2
  • FortiManager 7.6.0 through 7.6.7
  • FortiManager Cloud 8.0.1 through 8.0.2
  • FortiManager Cloud 7.6.0 through 7.6.7
  • FortiSASE Sovereign 25, 25.3 and 25.4 (all versions in these branches)

Vulnerable configuration: JSON API access enabled on an administrative profile. This is disabled by default.

Not affected: the 7.4 and 7.2 branches of FortiAnalyzer, FortiManager, their Cloud variants and FortiAnalyzer BigData. Cloud hosting does not by itself remove exposure, since the Cloud products have explicit affected ranges.

Vendor security history

Fortinet's PSIRT states that it publishes remediated findings whether they were discovered internally or externally, and issues a monthly advisory on the second Tuesday. For this issue, the advisory credits internal discovery, provides a workaround, and separates affected from unaffected branches.

FortiManager has a history of real-world exploitation. Mandiant investigated CVE-2024-47575, a different FortiManager flaw, and tracked mass exploitation by UNC5820 involving more than 50 potentially compromised FortiManager devices, with activity observed as early as June 27, 2024. The actor staged and exfiltrated configuration data from managed FortiGate devices, including detailed configurations, user information and FortiOS256-hashed passwords. Mandiant found no evidence that the data was used for further compromise or lateral movement.

In April 2025, CISA reported a post-exploitation technique on FortiGate devices in which a threat actor used previously exploited Fortinet vulnerabilities to create a malicious file, potentially allowing read-only access to device files including configurations. Fortinet contacted identified affected account holders with mitigation guidance.

Both cases involve different vulnerabilities and products. UNC5820 should not be attributed to CVE-2026-126170, and neither case indicates exploitation of this CVE.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization