Fortinet has disclosed a critical security vulnerability affecting multiple products in its centralized network management and security analytics portfolio.
Tracked as CVE-2026-126170, the vulnerability is caused by improper encoding or escaping of output in the JSON-RPC API.
An unauthenticated attacker with network access to the vulnerable API may send a specially crafted HTTP request and potentially execute unauthorized commands on the affected system.
The vulnerability has a CVSS 3.1 score of 9.8 (Critical), reflecting its potential for remote exploitation without authentication or user interaction.
Affected products include:
FortiManager
FortiAnalyzer
FortiManager Cloud
FortiAnalyzer Cloud
FortiAnalyzer-BigData
However, the vulnerability is conditional: the JSON API must be enabled on an administrative profile. Fortinet states that this functionality is disabled by default.
A public proof of concept was reported on GitHub on November 11, 2026. Although public exploit code increases the possibility of exploitation attempts, the available reporting does not establish confirmed attacks in the wild.
Organizations should identify affected Fortinet deployments, review JSON API configuration, restrict access to management interfaces, and follow Fortinet's official remediation guidance.
Vulnerability Details
Attribute | Details |
|---|---|
CVE ID | CVE-2026-126170 |
Vendor | Fortinet |
Vulnerability Type | Improper Encoding or Escaping of Output |
Affected Component | JSON-RPC API |
CVSS Version | CVSS 3.1 |
CVSS Score | 9.8 |
Severity | Critical |
CWE | CWE-116 |
Authentication Required | No |
User Interaction | None |
Attack Vector | Network |
Exploitation Status | Public PoC reported; no confirmed in-the-wild exploitation in the reviewed sources |
Vendor Advisory | FG-IR-26-219 |
Technical Description
CVE-2026-126170 is an improper output encoding vulnerability affecting the JSON-RPC API used by Fortinet management products.
Output encoding is a security mechanism that ensures data is represented safely before being processed by another component. When output is not correctly encoded or escaped, specially crafted input may alter how the receiving component interprets the resulting data.
In this case, an attacker can potentially manipulate JSON-RPC request processing through a specially crafted HTTP request, resulting in unauthorized command or code execution.
The vulnerability is particularly significant because successful exploitation does not require valid authentication or user interaction.
However, the JSON API must be enabled on the affected administrative profile. Fortinet states that this functionality is disabled by default.
This means that version identification alone is insufficient to determine exposure. Organizations must also verify whether the vulnerable API functionality is enabled.
CVSS 3.1 Breakdown
Metric | Value |
|---|---|
Attack Vector (AV) | Network |
Attack Complexity (AC) | Low |
Privileges Required (PR) | None |
User Interaction (UI) | None |
Scope (S) | Unchanged |
Confidentiality (C) | High |
Integrity (I) | High |
Availability (A) | High |
Base Score | 9.8 |
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Products and Versions
The following affected version ranges are reported for CVE-2026-126170.
Product | Affected Versions |
|---|---|
FortiManager | 7.6.0 – 7.6.7 |
FortiManager | 8.0.0 – 8.0.2 |
FortiAnalyzer | 7.6.0 – 7.6.7 |
FortiAnalyzer | 8.0.0 – 8.0.2 |
FortiManager Cloud | 7.6.0 – 7.6.7 |
FortiManager Cloud | 8.0.1 – 8.0.2 |
FortiAnalyzer Cloud | 7.6.0 – 7.6.7 |
FortiAnalyzer Cloud | 8.0.1 – 8.0.2 |
FortiAnalyzer-BigData | 7.6.0 – 7.6.2 |
Important exposure condition: The JSON API must be enabled. Fortinet indicates that this functionality is disabled by default.
Organizations should verify the exact affected and fixed version matrix in the official Fortinet advisory before scheduling upgrades. Do not assume that a fixed version for one product or branch automatically applies to every affected product.
Attack Overview
1. Identification of Exposed Fortinet Management Systems
An attacker may identify FortiManager and FortiAnalyzer systems accessible over a network and determine whether their JSON-RPC API functionality is exposed.
Internet accessibility is not the only relevant factor. Internal systems reachable from untrusted or compromised network segments may also require assessment.
2. Crafted JSON-RPC Request
The attacker sends a specially crafted HTTP request to the vulnerable JSON-RPC API.
The vulnerability involves improper output encoding or escaping, which may cause the application to interpret attacker-controlled data in an unintended manner.
3. Unauthorized Command Execution
If the affected version and required API configuration are present, successful exploitation may allow the attacker to execute unauthorized commands without authentication.
The available advisory information does not establish a complete exploitation chain or provide sufficient technical detail to describe the exact command-execution mechanism.
4. Potential Post-Exploitation Activity
If an attacker obtains command execution on a Fortinet management appliance, potential follow-on activities could include:
Accessing sensitive management information.
Inspecting device configurations and administrative data.
Modifying system configurations.
Attempting to establish persistence.
Accessing information associated with centrally managed infrastructure.
Attempting lateral movement into connected management networks.
These are potential consequences of successful compromise, not confirmed post-exploitation activities associated with this specific CVE.
Public Proof of Concept and Exploitation Status
A public proof of concept associated with CVE-2026-126170 was reported on GitHub on November 11, 2026.
Repository reported by cve.now:
Ghost-Bx1/cve-2026-126170-fortimanager-jsonrpc-rce
The availability of public exploit code may reduce the effort required for attackers to develop or adapt exploitation attempts.
However, the distinction between public exploit availability and confirmed exploitation is important.
Assessment | Status |
|---|---|
Public proof of concept | Reported available |
Confirmed exploitation in the wild | Not established in reviewed sources |
CISA Known Exploited Vulnerabilities listing | Not listed in the cve.now check dated November 11, 2026 |
Vendor remediation guidance | Available through Fortinet advisory |
Risk priority | Critical |
Organizations should not wait for confirmation of exploitation before applying remediation.
Threat Hunting Recommendations
Although dedicated IOCs are unavailable, security teams can investigate suspicious activity involving:
Unexpected HTTP requests to FortiManager and FortiAnalyzer JSON-RPC interfaces.
Unusual API requests originating from external or unauthorized internal IP addresses.
Unexpected administrative configuration changes.
Suspicious command execution on Fortinet management appliances.
Unusual outbound network connections from management systems.
Unexpected account creation or privilege modifications.
Abnormal access to centrally managed firewall configurations.
Correlate API access logs, administrative audit records, network telemetry, and available appliance logs to identify suspicious activity.
Potential Impact
Successful exploitation of CVE-2026-126170 could have serious consequences for organizations using Fortinet management infrastructure.
Remote Command Execution: An unauthenticated attacker may execute unauthorized commands on an affected system.
Sensitive Information Exposure: Compromise of management appliances could expose administrative information, device configurations, and other sensitive operational data.
Configuration Manipulation: Attackers may potentially modify management settings or configurations, depending on the level of access obtained.
Security Monitoring Disruption: Compromise of centralized security management infrastructure could affect the integrity and availability of security operations.
Enterprise Network Exposure: FortiManager and FortiAnalyzer may have visibility into or administrative relationships with multiple network security devices. Compromise could therefore create opportunities for broader attacks.
Operational Disruption: Successful exploitation could affect management services and potentially interfere with normal security administration.
These impacts describe potential outcomes; they are not evidence that every affected deployment will experience these consequences.
Recommendations
Immediate Actions
Identify Affected Assets: Inventory all FortiManager, FortiAnalyzer, FortiManager Cloud, FortiAnalyzer Cloud, and FortiAnalyzer-BigData deployments.
Verify Software Versions: Compare actual running versions against the affected ranges and confirm whether vendor fixes or applicable backports have been installed.
Check JSON API Configuration: Determine whether the JSON API is enabled on administrative profiles. This is a required exposure condition and is disabled by default.
Disable Unnecessary JSON API Access: If the JSON API is not required, follow Fortinet's workaround by setting
rpc-permittononeon affected administrative profiles.Apply Vendor Security Updates: Upgrade affected products to the appropriate fixed releases identified in Fortinet's official FG-IR-26-219 advisory.
Restrict Management Access: Limit access to Fortinet management interfaces and APIs to trusted administrative networks and authorized source addresses.
Review API Activity: Investigate unusual JSON-RPC requests, unexpected source IP addresses, and abnormal API usage.
Inspect Administrative Changes: Review unexpected administrator account creation, permission changes, configuration modifications, and suspicious management operations.
Monitor Outbound Connections: Investigate unusual outbound traffic originating from FortiManager and FortiAnalyzer appliances.
Preserve Evidence: Retain relevant system logs, administrative audit records, network telemetry, and configuration backups if suspicious activity is identified.
Assess Potential Compromise: If unauthorized command execution is suspected, initiate incident response and investigate the appliance and connected management infrastructure.
Preventive Actions
Minimize API Exposure: Enable JSON API functionality only for administrative workflows that explicitly require it.
Implement Network Segmentation: Isolate Fortinet management appliances from user networks and general-purpose infrastructure.
Enforce Least Privilege: Restrict administrative profiles and API permissions to the minimum required operations.
Strengthen Administrative Authentication: Enforce strong authentication and MFA for management access wherever supported.
Implement Configuration Monitoring: Monitor Fortinet appliance configurations for unauthorized changes.
Centralize Security Logging: Forward available administrative, system, and network logs to a centralized SIEM platform.
Review Management Access Regularly: Audit authorized administrators, API profiles, trusted source addresses, and automation accounts.
Maintain Patch Compliance: Include FortiManager and FortiAnalyzer in emergency vulnerability management procedures.
Monitor Public Exploit Development: Track changes to the reported proof-of-concept repository and vendor security advisories.
Conduct Continuous Threat Hunting: Correlate API access, system activity, configuration changes, and network connections to identify potential exploitation attempts.
MITRE ATT&CK Mapping
Tactic | Technique ID | Technique |
|---|---|---|
Initial Access | T1190 | Exploit Public-Facing Application |
Execution | T1059 | Command and Scripting Interpreter |
Discovery | T1082 | System Information Discovery |
Discovery | T1016 | System Network Configuration Discovery |
Persistence | T1136 | Create Account – potential post-compromise behavior |
Defense Evasion | T1562.001 | Impair Defenses – potential post-compromise behavior |
Command and Control | T1071.001 | Web Protocols |
The mappings are suggested based on the potential exploitation and post-compromise capabilities. The vendor advisory does not confirm that these follow-on techniques have been observed in attacks involving CVE-2026-126170.
Conclusion
CVE-2026-126170 represents a critical security risk to organizations operating affected Fortinet management products with the JSON API enabled.
With a CVSS score of 9.8, no authentication requirement, and public proof-of-concept code reported on November 11, 2026, the vulnerability deserves immediate attention from infrastructure and security teams.
Although the JSON API is disabled by default, organizations should verify the actual configuration of every deployment rather than assume that the feature remains disabled.
Security teams should prioritize identifying affected systems, disabling unnecessary API access, restricting management interfaces, and applying the appropriate Fortinet security updates.
The compromise of centralized management infrastructure can have implications beyond an individual appliance, making timely remediation and continuous monitoring particularly important.
