CVE Intelligence
CISA KEV High File handling

CVE-2022-41328 — Fortinet FortiOS Path Traversal Vulnerability

A improper limitation of a pathname to a restricted directory vulnerability ('path traversal') [CWE-22] in Fortinet FortiOS version 7.2.0 through 7.2.3, 7.0.0 through 7.0.9 and before 6.4.11 allows a privileged attacker to read and write files on the underlying Linux system via crafted CLI commands.

Published Mar 7, 2023 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: fortinet

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · Mar 14, 2023 ☠ UNC3886
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Exploited by 1 threat actor(s) (MITRE ATT&CK)+10
  • EPSS 10.7% (30-day exploitation probability)+14
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Mar 14, 2023
EPSS FIRST
10.68%
ahead of 96% of scored CVEs · Oct 14, 2026
Affects
Fortinet
Fortios
CVSS base
7.1
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Apr 4, 2023 — passed 1290 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Fortinet Fortios).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. EPSS ahead of 96% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Fortinet Fortios ≥ 6.0.0 and ≤ 6.0.16≥ 6.2.0 and < 6.2.14≥ 6.4.0 and < 6.4.12≥ 7.0.0 and < 7.0.10≥ 7.2.0 and < 7.2.4 Vulnerable NIST National Vulnerability Database
Fortinet Fortios ≥ 7.2.0 and ≤ 7.2.3≥ 7.0.0 and ≤ 7.0.9≥ 6.4.0 and ≤ 6.4.11≥ 6.2.0 and ≤ 6.2.13≥ 6.0.0 and ≤ 6.0.16 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.1 CVSS 3.1 High 1.8 5.2 nvd@nist.gov via NIST National Vulnerability Database
7.1 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
6.7 CVSS 3.1 Medium 0.8 5.9 psirt@fortinet.com via NIST National Vulnerability Database
6.5 CVSS 3.1 Medium — — fortinet via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 7.1 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-22 · Path Traversal

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Mar 14, 2023
Federal deadline
Apr 4, 2023
passed 1290 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Threat actors exploiting this CVE MITRE ATT&CK

According to MITRE ATT&CK.

UNC3886 G1048

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 10.68%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Monitor file creation in web directories and paths with traversal sequences (../).
  • Hunt retroactively in logs from before Mar 14, 2023 (KEV listing): exploitation may have started earlier.
endpoint telemetry (EDR)file integrity (FIM)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · fortinet/fortios
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Affected products added · fortinet/fortios
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.1
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2023
  • Added to CISA KEV catalog
    Mar 13, 2023 · CISA
  • CVE published
    Mar 7, 2023 · fortinet

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

Fortinet
every CVE for this vendor
2023-03
what else CISA listed that month
File handling
same class
CWE-22
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-106175 A Double Free vulnerability [CWE-415] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.7,... 2d
  • CVE-2026-84393 A improper validation of certificate with host mismatch vulnerability in Fortinet FortiOS 7.6.1... Sep 8, 2026
  • CVE-2026-84392 A NULL Pointer Dereference vulnerability [CWE-476] vulnerability in Fortinet FortiOS 7.4 all... Sep 8, 2026
  • CVE-2026-71408 A allocation of resources without limits or throttling vulnerability in Fortinet FortiOS 7.6.0... Aug 12, 2026
  • CVE-2026-71407 Stack-based Buffer Overflow in Fortinet Fortios Aug 12, 2026
  • CVE-2026-59839 Path Traversal in Fortinet Fortiproxy Jul 14, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2022-41328 is "Fortinet FortiOS Path Traversal Vulnerability", rated High. It affects Fortios (Fortinet); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.1 describes technical severity. EPSS 10.68% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.