Automated Threat Modeling

Brief Summary: FortiAnalyzer and FortiManager CVE-2026-126262, an Unauthenticated SQL Injection via Crafted OFTP Packets

A brief summary of CVE-2026-126262, a critical unauthenticated SQL injection in the OFTP log transfer service of Fortinet FortiAnalyzer and FortiManager with FortiAnalyzer features. Covers the attack surface, affected versions, and the product-specific fixed builds from FG-IR-26-276.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Brief Summary: FortiAnalyzer and FortiManager CVE-2026-126262, an Unauthenticated SQL Injection via Crafted OFTP Packets

Introduction

In many Fortinet deployments, FortiAnalyzer and FortiManager receive logs from FortiGate firewalls and power the event views and reports that security teams use every day. A newly disclosed SQL injection in the protocol those appliances use to receive logs means that an unauthenticated attacker who can reach the OFTP port may be able to execute code or commands on the systems that hold an organization's security visibility.

Fortinet tracks the issue as FG-IR-26-276, first published on November 10, 2026. NVD published the record on November 11, 2026. The input CVE record lists the vendor as Unknown, but the affected vendor (and the CNA supplying the score) is Fortinet, Inc. Fortinet currently marks the issue as Known Exploited: No, the November 11 Health ISAC bulletin reports no active exploitation, and the CVE is absent from CISA KEV catalog version 2026.11.10 (a snapshot that predates NVD publication). We found no actor attribution, public exploit, or CVE-specific indicators of compromise in the reviewed sources. This reflects current reporting and is no guarantee that exploitation will not occur.

Technical information

Root cause: CWE 89 behind a log transfer protocol

Fortinet classifies the bug as improper neutralization of special elements used in an SQL command (CWE 89). MITRE's definition of this weakness describes externally influenced input altering the intended SQL command because special elements are not neutralized correctly. In this case, the externally influenced input arrives inside crafted OFTP packets, and the stated consequence is possible execution of unauthorized code or commands on the appliance.

The scope covers FortiAnalyzer and FortiManager with FortiAnalyzer features. Those features let FortiManager store logs and provide log analysis, incident and event views, and reports, which is why a log ingestion protocol handler is present on FortiManager at all. When you review FortiManager inventory, check the enabled feature set as well as the firmware version. Neither the advisory nor the feature documentation establishes disabling those features as a validated workaround.

What OFTP is and where it listens

OFTP stands for Optimized Fabric Transfer Protocol. Fortinet documents it for synchronization between FortiGate and FortiAnalyzer, and for remote logging and archiving to FortiAnalyzer or FortiManager. The FortiAnalyzer 8.0 incoming ports reference lists TCP/514 for OFTP traffic from FortiGate and FortiManager. An older OFTP overview mentions both TCP/514 and UDP/514. Neither that overview nor the advisory establishes that both transports are exploitable.

In practice, exposure assessment has to include the log transfer listener, not only the administrative GUI or login surface. Restricting administrator access with trusted hosts protects administrative logins, but no source establishes it as protection for unauthenticated OFTP processing.

Attack flow

Based on the published description, the attack sequence at a high level is:

  1. The attacker obtains network reachability to the OFTP service on an affected FortiAnalyzer, or on a FortiManager with FortiAnalyzer features enabled.
  2. No authentication is required. The attacker sends crafted OFTP packets to the service.
  3. Attacker-controlled content in those packets reaches an SQL statement without proper neutralization, resulting in SQL injection.
  4. The injection may lead to execution of code or commands on the underlying system.

What the advisory does not say

Fortinet does not disclose the vulnerable SQL statement, the database engine, the specific packet field, the parser function, or how the SQL injection transitions into command execution. FortiAnalyzer and FortiManager are closed source appliances, so there is no public commit or diff to inspect. Reconstructing a more detailed exploit chain would go beyond the published evidence, and we have not attempted to do so.

Severity scoring

NVD has not yet supplied its own assessment. It displays the Fortinet CNA-supplied base score of 9.8 Critical:

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

Fortinet's advisory page displays 9.3, with a vector that additionally includes the temporal metrics E:P/RL:O/RC:C. Under the FIRST CVSS 3.1 framework, temporal metrics (exploit code maturity, remediation level, report confidence) adjust the base score, which explains the difference. RL:O (Remediation Level: Official Fix) also confirms that a vendor-shipped fix exists. The network vector, low complexity, and lack of required privileges or user interaction mean that anyone who can reach the OFTP port can attempt the attack.

Patch information

Fortinet has released fixed firmware for every affected branch of FortiAnalyzer (FAZ) and for FortiManager (FMG) units with FortiAnalyzer features. Fortinet delivers the fix only as full firmware builds. There is no hotfix and no public source patch, and the advisory's Virtual Patch field is "No", so there is no IPS signature to deploy in front of the appliance. Installing fixed firmware is the only vendor remediation.

Fixed builds by branch

  • FortiAnalyzer 8.0: vulnerable 8.0.0 through 8.0.1; upgrade to 8.0.2 or above
  • FortiAnalyzer 7.6: vulnerable 7.6.0 through 7.6.7; upgrade to 7.6.8 or above
  • FortiAnalyzer 7.4: vulnerable 7.4.0 through 7.4.11; upgrade to 7.4.12 or above
  • FortiAnalyzer 7.2: vulnerable 7.2.0 through 7.2.12; upgrade to 7.2.13 or above
  • FortiManager 8.0: vulnerable 8.0.0; upgrade to 8.0.1 or above
  • FortiManager 7.6: vulnerable 7.6.0 through 7.6.7; upgrade to 7.6.8 or above
  • FortiManager 7.4: vulnerable 7.4.0 through 7.4.11; upgrade to 7.4.12 or above
  • FortiManager 7.2: vulnerable 7.2.0 through 7.2.12; upgrade to 7.2.13 or above

The CVE record from Fortinet lists the same targets in its solutions field: FMG 8.0.1, 7.6.8, 7.4.12 and 7.2.13, and FAZ 8.0.2, 7.6.8, 7.4.12 and 7.2.13.

The 8.0 branch is split between products

The fix landed in different 8.0 releases for each product. FortiManager is fixed in 8.0.1, but FortiAnalyzer 8.0.1 is still vulnerable and needs 8.0.2. If you run both products, standardizing on 8.0.1 everywhere is not sufficient. Check each FortiAnalyzer against its own row. On the 7.6, 7.4 and 7.2 branches, both products share the same fixed version.

What the fix covers

Fortinet does not describe the code change. In general, fixing this bug class means fields taken from the protocol are passed to the database layer as bound parameters or are strictly validated, instead of being concatenated into SQL text. Treat that as a description of the bug class, not a confirmed account of Fortinet's change. The verified fact is that the fixed builds above remove the vulnerable behavior.

  • The same release fixed a second unauthenticated OFTP bug, an SSRF tracked as CVE-2026-126260 (FG-IR-26-274). Its fixed versions are different (for example, FMG 7.6.7 for that bug), so a unit patched for one OFTP issue is not automatically patched for the other. Moving FAZ and FMG to the versions listed above closes both. InfoSec Monkey's tracking points to 7.6.8 as the build that covers all of that release's FAZ/FMG advisories on the 7.6 branch.
  • Separately, the FG-IR-26-219 advisory for CVE-2026-126170 (a JSON API issue) lists FortiAnalyzer 8.0.0 through 8.0.2 as affected and points to an upcoming 8.0.3 or a JSON API workaround. FortiAnalyzer 8.0.2 therefore closes CVE-2026-126262 but not every contemporaneous Fortinet issue. That JSON API workaround is not a mitigation for this CVE.

Deployment notes

  • Cyber Security News reports that Fortinet shipped the updated builds before publishing the November advisories, so some estates may already run a fixed version. Confirm the exact build number on each unit rather than assuming.
  • Use Fortinet's upgrade path tool before moving to a new branch, and upgrade FortiManager and FortiAnalyzer before the FortiGates they manage.
  • Health ISAC recommends applying official updates promptly after appropriate predeployment testing.

Supplementary hardening (not a fix)

Fortinet's FortiAnalyzer security best practices recommend placing FortiAnalyzer behind a firewall to limit access attempts, disabling unused interfaces, limiting administrator access with trusted hosts, and using named accounts with logs sent to a central destination. Health ISAC adds network segmentation to shield critical internal systems. These controls reduce exposure and improve oversight, but none of them is established as correcting the vulnerable OFTP handling. Fortinet's OFTP TLS and stronger encryption settings concern transport security and are likewise not established as a fix for this SQL injection.

Affected systems and versions

FortiAnalyzer

  • 8.0.0 through 8.0.1
  • 7.6.0 through 7.6.7
  • 7.4.0 through 7.4.11
  • 7.2.0 through 7.2.12

FortiManager (with FortiAnalyzer features)

  • 8.0.0
  • 7.6.0 through 7.6.7
  • 7.4.0 through 7.4.11
  • 7.2.0 through 7.2.12

Vulnerable configuration: an affected build with a reachable OFTP service (TCP/514 per the FortiAnalyzer 8.0 ports reference). No authentication is required. For FortiManager, the advisory qualifies scope by the presence of FortiAnalyzer features. Do not extend this list to unlisted products or releases without further vendor guidance.

Vendor security history

This flaw came out of Fortinet's own internal discovery process. Fortinet credits its Product Security team, Gwendal Guégniaud and Theo Leleu, who found the flaw internally with the help of an AI model (Claude Mythos), and thanks Joshua Foote of JP Morgan Chase's XOR team, who reported it independently. Fortinet's published PSIRT policy describes secure coding training, security testing, monthly advisories, and accelerated publication when active exploitation increases customer risk.

Fortinet management infrastructure has also been exploited in the past. CVE-2024-47575, a separate FortiManager vulnerability, was exploited by UNC5820 as early as June 27, 2024. Mandiant investigated more than 50 potentially compromised FortiManager devices and found the actor staged and exfiltrated configuration data from managed FortiGates, including user information and hashed passwords, with connections involving TCP/541. Mandiant found no evidence of lateral movement using that data. CISA later noted Fortinet's updated workarounds and indicators and added that CVE to KEV.

That history is context, not attribution. CVE-2024-47575 involves a different vulnerability and protocol, and nothing in the reviewed material links CVE-2026-126262 to UNC5820.

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