CVE
A path traversal: '../filedir' vulnerability in Fortinet FortiOS 8.0.0 through 8.0.1, FortiOS 7.6.0 through 7.6.7, FortiOS 7.4.0 through…
FortiOS 7.2.0 through 8.0.1 and FortiPAM 1.0.0 through 1.6.2 are affected only when GPC OS Login is enabled. CVSS scores it 7.4. No fixed version is listed in the checked facts.
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
- Not reported
Do first: Workaround: The checked facts give no workaround. The only stated limit is the condition that GPC OS Login is enabled, so the advisory's own wording points to that setting as the factor that matters until a fix is available.
- 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? →
- 43/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? →
- Unclear
- 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
Fortinet FortiOS and FortiPAM contain a path traversal flaw that lets an unauthenticated attacker bypass authentication using specially crafted credentials. The attacker can reach it remotely over the network without logging in.
Read the original description
A path traversal: '../filedir' vulnerability in Fortinet FortiOS 8.0.0 through 8.0.1, FortiOS 7.6.0 through 7.6.7, FortiOS 7.4.0 through 7.4.12, FortiOS 7.2.0 through 7.2.13, FortiPAM 1.6 all versions, FortiPAM 1.5 all versions, FortiPAM 1.4 all versions, FortiPAM 1.3 all versions, FortiPAM 1.2 all versions, FortiPAM 1.1 all versions, FortiPAM 1.0 all versions may allow an unauthenticated attacker to bypass authentication via specially crafted credentials.
Who should check
Teams running FortiOS 7.2 to 8.0 builds with GPC OS Login enabled, and teams running FortiPAM 1.0 to 1.6 (migrate to a fixed release).
Read the source excerpt
“The product is impacted only if GPC OS Login is enabled.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach14/20Affects Fortinet (an enterprise product or network appliance)
- Severity7.4/10CVSS 7.4
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 88 if added to CISA KEV
- Would score about 83 if CISA's SSVC rates exploitation active
- Would score about 48 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts give no workaround. The only stated limit is the condition that GPC OS Login is enabled, so the advisory's own wording points to that setting as the factor that matters until a fix is available.
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-126255 (A path traversal: '../filedir' vulnerability in Fortinet FortiOS 8.0.0 through 8.0.1, FortiOS 7.6.0 through 7.6.7, FortiOS 7.4.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-126255 (entry last updated 2026-11-11):
Affected:
- Fortinet FortiOS: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.12; from 7.2.0, through 7.2.13
- Fortinet FortiPAM: from 1.6.0, through 1.6.2; from 1.5.0, through 1.5.1; from 1.4.0, through 1.4.3; from 1.3.0, through 1.3.1; from 1.1.0, through 1.1.2; from 1.0.0, through 1.0.3
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- GPC OS Login is enabled (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-269)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126255 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126255 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-269
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-126255
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-126255"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Fortinet FortiOS
From 8.0.0 · through 8.0.1; From 7.6.0 · through 7.6.7; From 7.4.0 · through 7.4.12; From 7.2.0 · through 7.2.13
- Fortinet FortiPAM
From 1.6.0 · through 1.6.2; From 1.5.0 · through 1.5.1; From 1.4.0 · through 1.4.3; From 1.3.0 · through 1.3.1; From 1.1.0 · through 1.1.2; From 1.0.0 · through 1.0.3
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-126255
Is CVE-2026-126255 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?
A path traversal flaw in the '../filedir' path lets an unauthenticated attacker bypass authentication using specially crafted credentials. The advisory's impact field also lists denial of service.Source: fortiguard.fortinet.com
Which versions are affected by CVE-2026-126255?
FortiOS: from 8.0.0 through 8.0.1; from 7.6.0 through 7.6.7; from 7.4.0 through 7.4.12; from 7.2.0 through 7.2.13. FortiPAM: from 1.6.0 through 1.6.2; from 1.5.0 through 1.5.1; from 1.4.0 through 1.4.3; from 1.3.0 through 1.3.1; from 1.1.0 through 1.1.2; from 1.0.0 through 1.0.3.Source: cve.now feed data
Am I affected, and how do I check?
FortiOS 8.0.0 through 8.0.1, 7.6.0 through 7.6.7, 7.4.0 through 7.4.12, and 7.2.0 through 7.2.13 are listed. FortiPAM 1.0.0 through 1.6.2 is also listed. The product is impacted only if GPC OS Login is enabled, so check the version and whether that setting is on.Source: fortiguard.fortinet.com
How do I fix CVE-2026-126255?
The checked facts do not name a fixed version or an upgrade target. Check the Fortinet advisory for the fixed release before planning an upgrade.Source: fortiguard.fortinet.com
What if there's no patch?
The checked facts give no workaround. The only stated limit is the condition that GPC OS Login is enabled, so the advisory's own wording points to that setting as the factor that matters until a fix is available.Source: fortiguard.fortinet.com