Introduction
Fortinet has fixed an authenticated SQL injection in the JSON RPC API used by FortiManager and FortiAnalyzer, the platforms many organizations rely on to administer Fortinet devices and centralize security telemetry. Because a crafted API request may lead to unauthorized code or command execution on these management systems, the issue carries a CVSS v3.1 base score of 8.8 even though no exploitation has been reported.
For context on the affected products: Fortinet reports that it was founded in 2000, sells over 50 enterprise-grade products, and has more than 1,000,000 customers (vendor-reported figures). FortiManager centralizes configuration, deployment, maintenance, and security policy administration for Fortinet devices, while FortiAnalyzer aggregates logs and telemetry from Fortinet and third-party systems for analytics and correlation. That concentration of administrative control and visibility is why flaws in these products matter operationally, although nothing in the sources indicates that this CVE has affected managed devices or telemetry anywhere.
NVD lists the vendor as "Unknown". The advisory, FG-IR-26-221, confirms the vendor is Fortinet.
Technical information
Root cause
Fortinet classifies CVE-2026-126175 as CWE-89: Improper Neutralization of Special Elements used in an SQL Command, in the API component. The reachable interface is the JSON RPC management API, which FortiManager and FortiAnalyzer use for nearly all administrative and automation traffic.
According to the available patch information, an authenticated attacker could get unsanitized input from a JSON RPC parameter into a backend SQL statement. Fortinet states that this may allow the attacker to execute unauthorized code or commands.
MITRE's general description of CWE-89 explains the weakness class: when an application concatenates user input into an SQL query, that input can alter the query's logic. This describes the class of bug, not the specific implementation inside FortiManager or FortiAnalyzer.
Severity and scoring
Fortinet, as the CNA, published the following vector, which NVD displays without its own independent assessment:
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Base score: 8.8 (High)
- Temporal score listed by Fortinet: 8.3
- VulniPulse shows the temporal metric
RL:O(Remediation Level: Official Fix), consistent with an official vendor fix being available.
The vector says the attack is network reachable and low complexity, requires low privileges (an authenticated session), and needs no user interaction. It is not an authentication bypass.
Attack flow
Based only on what the advisory discloses, the sequence looks like this:
- The attacker holds valid credentials for the FortiManager or FortiAnalyzer JSON RPC API (PR:L).
- The attacker sends a crafted JSON RPC request in which a parameter carries SQL special elements.
- The affected handler places that parameter into a backend SQL statement without proper neutralization.
- The altered SQL execution may lead to unauthorized code or command execution on the system.
What is not disclosed
The advisory does not identify the vulnerable endpoint or API method, the affected JSON field, the backend database engine, a payload, the specific administrator role required, or the mechanism that turns SQL injection into code or command execution. FortiAnalyzer and FortiManager are closed source, so there is no public commit, diff, or code-level changelog.
Fortinet has not described the code change. For this kind of bug, the standard fix is to stop building SQL strings from request fields and use parameterized queries or strict input validation in the affected handler. That is an inference about the usual approach, not a vendor-confirmed detail. In our view, exposure decisions should rest on product and version data rather than on guesses about ports, methods, or payloads.
Patch information
Fortinet's fix ships as firmware updates published in PSIRT advisory FG-IR-26-221 on 2026-11-10. NVD lists that advisory as its only vendor reference, and NVD publication followed on 2026-11-11.
Fixed releases (from FG-IR-26-221)
FortiAnalyzer
- 8.0: not affected
- 7.6.0 through 7.6.7: upgrade to 7.6.8 or above
- 7.4.0 through 7.4.11: upgrade to 7.4.12 or above
- 7.2.2 through 7.2.12: migrate to a fixed release (no 7.2 fix listed)
FortiAnalyzer Cloud
- 8.0: not affected
- 7.6.0 through 7.6.7: upgrade to 7.6.8 or above
- 7.4.1 through 7.4.11: upgrade to 7.4.12 or above
- 7.2.2 through 7.2.12: upgrade to 7.2.13 or above
FortiManager
- 8.0: not affected
- 7.6.0 through 7.6.7: upgrade to 7.6.8 or above
- 7.4.0 through 7.4.11: upgrade to 7.4.12 or above
- 7.2.2 through 7.2.12: migrate to a fixed release
FortiManager Cloud
- 8.0: not affected
- 7.6, all versions: migrate to a fixed release
- 7.4, all versions: migrate to a fixed release
- 7.2.2 through 7.2.13: migrate to a fixed release
The fixes are in 7.6.8 and 7.4.12. The 8.0 branch was never affected, so moving to 8.0 is also a fix path. On-premises 7.2 gets no backport, so those deployments have to move to a newer fixed branch. FortiAnalyzer Cloud 7.2 is the only 7.2 line with a fix inside its own branch, 7.2.13.
Discrepancies between the advisory and NVD
- FortiAnalyzer Cloud 7.2: The advisory lists 7.2.13 as the fix, but the CVE text on NVD says FortiAnalyzer Cloud is affected through 7.2.13. Treat 7.2.13 cautiously until Fortinet clarifies, and record the discrepancy in remediation tracking.
- FortiManager Cloud 7.6 and 7.4: The advisory says all versions are affected and gives no fix within those branches, while NVD lists only 7.6.0 through 7.6.7 and 7.4.1 through 7.4.11. Go by the advisory. For FortiManager Cloud, the remedy is a migration rather than a point upgrade, and appliance fix versions should not be assumed to apply to these Cloud branches.
No virtual patch or workaround
The advisory marks "Virtual Patch: No" and provides no workaround. Fortinet is not offering an IPS or WAF signature that blocks malicious JSON RPC payloads in the interim, so installing fixed firmware (or migrating) is the only vendor fix. The H-ISAC alert covering this and other Fortinet vulnerabilities recommends identifying exposed instances, prioritizing updates, validating system integrity, applying official updates after appropriate testing, enforcing least privilege, and segmenting the network. These are useful supplementary controls but are not demonstrated substitutes for the fix.
Discovery
Fortinet found the bug internally. Loic Pantano of the Fortinet Product Security team reported it with help from the AI model Claude Mythos. There was no outside disclosure timeline. Publication and fixed builds arrived together.
Detection methods
Right now, CVE-2026-126175 can only be detected by checking versions. Scanners can identify FortiManager and FortiAnalyzer systems running vulnerable builds, but as of 11 November 2026 no signature, IoC set, or rule has been published that catches actual exploitation. Keep those two goals separate when planning coverage.
Tenable Nessus plugins (version based)
Tenable released one plugin per on-premises product, both mapped to FG-IR-26-221:
- Plugin 378642, Fortinet FortiManager Improper neutralization of special elements used in an SQL command (FG-IR-26-221), file
fortimanager_FG-IR-26-221.nasl - Plugin 378643, Fortinet FortiAnalyzer Improper neutralization of special elements used in an SQL command (FG-IR-26-221), file
fortianalyzer_FG-IR-26-221.nasl
Both are in the Firewalls family, rated High, and are Local checks. Each requires the KB items Host/Fortigate/model and Host/Fortigate/version, which means Nessus must log in to the appliance and collect the model and firmware version first. An unauthenticated scan will usually miss these hosts, so make sure your scan policy has working credentials for FortiManager and FortiAnalyzer.
Tenable states that Nessus does not test the flaw itself and "relied only on the application's self-reported version number." A finding means the version is in the vulnerable range, not that the system was attacked. The plugins also only cover appliances you scan yourself. FortiAnalyzer Cloud and FortiManager Cloud are affected, but they are not hosts you can point Nessus at.
Rapid7 InsightVM and Nexpose
Rapid7's vulnerability database lists CVE-2026-126175 as "Covered by Rapid7" for Fortinet FortiManager, added 11 November 2026. The listing mentions only FortiManager, so confirm FortiAnalyzer coverage before relying on Rapid7 for it.
Manual or CMDB checks
Without a scanner, pull firmware versions from your asset inventory or FortiManager device records and compare them with the ranges in FG-IR-26-221:
- FortiManager and FortiAnalyzer: 7.6.0 through 7.6.7, 7.4.0 through 7.4.11, and 7.2.2 through 7.2.12
- FortiAnalyzer Cloud and FortiManager Cloud: 7.6.0 through 7.6.7, 7.4.1 through 7.4.11, and 7.2.2 through 7.2.13. Fortinet lists every FortiManager Cloud 7.6 and 7.4 release as affected, so treat any FortiManager Cloud instance on those branches as vulnerable.
- 8.0 builds: not affected in any of the four products. Watch the edges, too: 7.2.0 and 7.2.1 fall outside the stated 7.2 range.
For Cloud tenants, this version comparison is effectively the only option, since the scanner plugins do not reach them.
Exploitation detection: none published yet
The advisory mentions no FortiGuard IPS signature and gives no indicators. CVETodo's rule tracker shows "None published (Sigma / Suricata / YARA / Nuclei)" as of 11 November 2026, and reports no public exploit in Exploit-DB, Metasploit, GitHub PoC repositories, or Nuclei templates. The Nessus plugins likewise state "No known exploits are available."
The flaw description still suggests two hunting leads:
- Who is using the JSON RPC API. Every attempt must come from a valid account. Review which administrator and API accounts call the FortiManager and FortiAnalyzer JSON RPC interface, and investigate new accounts, unexpected source IPs, or low-privilege users suddenly generating heavy API traffic.
- Unusual JSON RPC activity in logs. CVETodo suggests watching for unusual log activity, especially JSON RPC requests. Since successful exploitation can lead to unauthorized code or command execution, look for appliance errors, database errors, or administrative changes that line up with unexplained API sessions.
These are hunting leads, not validated detections. No public source yet gives a specific request pattern, payload marker, or log string for this CVE. Check back with Fortinet (FortiGuard IPS and Outbreak updates), Tenable, and open rule repositories for exploit-specific content.
Threat status
Fortinet records "Known Exploited: No", and the H-ISAC alert dated November 11, 2026 reports no active exploitation for the vulnerability set it covers. No threat actor, campaign, or indicators are tied to this CVE in the reviewed sources. That reflects limited intelligence, not an assurance of safety.
Affected systems and versions
Per Fortinet's advisory FG-IR-26-221:
- FortiAnalyzer: 7.6.0 through 7.6.7; 7.4.0 through 7.4.11; 7.2.2 through 7.2.12
- FortiAnalyzer Cloud: 7.6.0 through 7.6.7; 7.4.1 through 7.4.11; 7.2.2 through 7.2.12 (NVD's description extends this to 7.2.13, which Fortinet lists as the fix)
- FortiManager: 7.6.0 through 7.6.7; 7.4.0 through 7.4.11; 7.2.2 through 7.2.12
- FortiManager Cloud: all 7.6 versions; all 7.4 versions; 7.2.2 through 7.2.13 (NVD lists bounded ranges of 7.6.0 through 7.6.7 and 7.4.1 through 7.4.11 for 7.6 and 7.4)
Not affected: the 8.0 branch of FortiAnalyzer, FortiAnalyzer Cloud, FortiManager, and FortiManager Cloud. Releases 7.2.0 and 7.2.1 fall outside the stated 7.2 ranges.
Vulnerable configuration: any affected build where an attacker can authenticate to the JSON RPC API. The advisory does not specify which account role is required.
Vendor security history
FortiManager has been targeted before. Mandiant investigated CVE-2024-47575, a different FortiManager vulnerability, and observed the cluster UNC5820 exploiting it as early as June 27, 2024. Working with Fortinet, Mandiant examined more than 50 potentially compromised FortiManager devices across industries. The observed outcome was staging and exfiltration of managed FortiGate configuration data, including user information and FortiOS256 hashed passwords. Mandiant stated that, at that stage, it had no evidence UNC5820 used the configurations to move laterally.
That earlier issue involved an unauthorized, attacker-controlled FortiManager device, while CVE-2026-126175 is an authenticated SQL injection through JSON RPC. The shared product does not imply a shared exploit, campaign, or actor. The history is relevant only because it shows why management infrastructure needs close attention. By contrast, the current issue was discovered internally and shipped with fixes at the time of disclosure.
References
- NVD entry for CVE-2026-126175
- CVE Record for CVE-2026-126175
- Fortinet PSIRT advisory FG-IR-26-221
- VulniPulse advisory for FG-IR-26-221
- Tenable Nessus plugin 378642 (FortiManager)
- Tenable Nessus plugin 378643 (FortiAnalyzer)
- Tenable CVE page for CVE-2026-126175
- Rapid7 vulnerability database entry
- CVETodo entry for CVE-2026-126175
- H-ISAC alert: Multiple Vulnerabilities in Fortinet Products (November 11, 2026)
- Mandiant: Investigating FortiManager Zero Day Exploitation (CVE-2024-47575)
- Fortinet: About Fortinet and the Security Fabric
- Fortinet CISO Collective: Security Hardening Release for Multiple Products
- FortiAnalyzer Data Sheet
- FortiManager Data Sheet
- MITRE CWE-89: SQL Injection



