CVE
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. 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).
- 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? →
- 34/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? →
- Specific setups only
- 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
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach14/20Affects Fortinet (an enterprise product or network appliance)
- Severity7.2/10CVSS 7.2
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 84 if added to CISA KEV
- Would score about 79 if CISA's SSVC rates exploitation active
- Would score about 41 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
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).Workaround: 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.
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-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"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- 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
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-126235
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: cve.now feed data
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: fortiguard.fortinet.com
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: cve.now feed data
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: fortiguard.fortinet.com
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: fortiguard.fortinet.com
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: fortiguard.fortinet.com