CVE
A improper neutralization of special elements used in an sql command ('sql injection') vulnerability in Fortinet FortiAnalyzer 8.0.0…
Affects FortiAnalyzer 7.2.0 through 8.0.1 and FortiManager 7.2.0 through 7.6.7 with FortiAnalyzer features, where the oftp port is reachable. No fix is listed.
Written by anthropic/claude-sonnet-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Do first: Workaround: No workaround is given in the available information. Because the attack needs access to the oftp port, limiting who can reach that port is relevant, and Fortinet's advisory should be checked for official guidance.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 45/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Fortinet FortiAnalyzer and FortiManager contain an SQL injection flaw that lets an attacker run code or commands on the system. The attacker can exploit it remotely, without logging in, by sending crafted OFTP packets to the oftp port.
Read the original description
A improper neutralization of special elements used in an sql command ('sql injection') vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer 7.4.0 through 7.4.11, FortiAnalyzer 7.2.0 through 7.2.12, FortiManager 8.0.0, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.11, FortiManager 7.2.0 through 7.2.12 may allow an unauthenticated attacker who has access to the oftp port to execute code or command on the system via crafted OFTP packets.
Who should check
Teams running Fortinet FortiAnalyzer 7.2–8.0, or FortiManager 7.2–8.0 with FortiAnalyzer features, where the oftp port is reachable by untrusted networks.
Read the source excerpt
“FortiAnalyzer or FortiManager with FortiAnalyzer features may allow an unauthenticated attacker who has access to the oftp port”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach14/20Affects Fortinet (an enterprise product or network appliance)
- Severity9.3/10CVSS 9.3
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 90 if added to CISA KEV
- Would score about 85 if CISA's SSVC rates exploitation active
- Would score about 50 if advisories confirm default setups are exposed
What to do
Workaround: No workaround is given in the available information. Because the attack needs access to the oftp port, limiting who can reach that port is relevant, and Fortinet's advisory should be checked for official guidance.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126262 (A improper neutralization of special elements used in an sql command ('sql injection') vulnerability in Fortinet FortiAnalyzer 8.0.0…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126262 (entry last updated 2026-11-11):
Affected:
- Fortinet FortiAnalyzer: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11; from 7.2.0, through 7.2.12
- Fortinet FortiManager: from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11; from 7.2.0, through 7.2.12
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- FortiManager 8.0.0, 7.6.0–7.6.7, 7.4.0–7.4.11 or 7.2.0–7.2.12 with FortiAnalyzer features (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-276)
- Attacker can reach the oftp port (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-276)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126262 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126262 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://fortiguard.fortinet.com/psirt/FG-IR-26-276
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126262
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126262"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Fortinet FortiAnalyzer
From 8.0.0 · through 8.0.1; From 7.6.0 · through 7.6.7; From 7.4.0 · through 7.4.11; From 7.2.0 · through 7.2.12
- Fortinet FortiManager
From 7.6.0 · through 7.6.7; From 7.4.0 · through 7.4.11; From 7.2.0 · through 7.2.12
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126262
Is CVE-2026-126262 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
This is an SQL injection flaw. Specially crafted OFTP packets could let an unauthenticated attacker who can reach the oftp port run code or commands on the system.Source: fortiguard.fortinet.com
Which versions are affected by CVE-2026-126262?
FortiAnalyzer: from 8.0.0 through 8.0.1; from 7.6.0 through 7.6.7; from 7.4.0 through 7.4.11; from 7.2.0 through 7.2.12. FortiManager: from 7.6.0 through 7.6.7; from 7.4.0 through 7.4.11; from 7.2.0 through 7.2.12.Source: cve.now feed data
Am I affected, and how do I check?
The listed ranges are FortiAnalyzer 7.2.0–7.2.12, 7.4.0–7.4.11, 7.6.0–7.6.7 and 8.0.0–8.0.1, and FortiManager 7.2.0–7.2.12, 7.4.0–7.4.11 and 7.6.0–7.6.7 with FortiAnalyzer features enabled. The software version shown in the device's system information can be compared with these ranges, and network access to the oftp port is also a condition.Source: fortiguard.fortinet.com
How do I fix CVE-2026-126262?
No fixed version is given in the available information. Check Fortinet's advisory for patched releases and upgrade once one is available.Source: fortiguard.fortinet.com
What if there's no patch?
No workaround is given in the available information. Because the attack needs access to the oftp port, limiting who can reach that port is relevant, and Fortinet's advisory should be checked for official guidance.Source: fortiguard.fortinet.com