dbcve.org
FortisoarApplication · Fortinet

CVE-2026-22573

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to after 7.6.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiSOAR PaaS 7.6.0 through 7.6.3, FortiSOAR PaaS 7.5 all versions, FortiSOAR PaaS 7.4 all versions, FortiSOAR PaaS 7.3 all versions, FortiSOAR on-premise 7.6.0 through 7.6.3, FortiSOAR on-premise 7.5 all versions, FortiSOAR on-premise 7.4 all versions, FortiSOAR on-premise 7.3 all versions may allow an authenticated remote attacker to perform path traversal attack via File Content Extraction actions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a path traversal vulnerability in FortiSOAR's File Content Extraction feature that allows authenticated remote attackers to access files outside the intended restricted directory through specially crafted pathname sequences.

MitigationUpgrade FortiSOAR to the latest version as specified by Fortinet's security advisory. If immediate upgrade is not possible, restrict file extraction functionality to trusted users and implement additional input validation on file paths.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortisoarApplication
Affected:>= 7.3.0, <= 7.3.3>= 7.4.0, <= 7.4.5>= 7.5.0, <= 7.5.3>= 7.6.0, <= 7.6.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed FortiSOAR version
    Log into the FortiSOAR admin UI and navigate to System Settings > About, or use the CLI command 'fwconsole --version' to retrieve the exact version number
    Affected if The version falls within 7.3.0-7.3.3, 7.4.0-7.4.5, 7.5.0-7.5.3, or 7.6.0-7.6.3
  2. Locate File Content Extraction feature configuration
    In FortiSOAR admin UI, go to Automation > Playbooks or Configuration > Extractors to find the File Content Extraction module settings
    Affected if The File Content Extraction feature is enabled and the version is in the affected range
  3. Verify extractor input configuration
    Review the File Content Extraction connector or extractor configuration to confirm it accepts file path inputs
    Affected if The extractor accepts file paths as input and version is in the affected range
  4. Assess user access to extraction functionality
    Check user roles and permissions in System Administration > Roles to determine which users have access to file extraction features
    Affected if Non-trusted or low-privilege users have access to the File Content Extraction feature and version is affected

Your environment is affected if FortiSOAR is running any version from 7.3.0 through 7.3.3, 7.4.0 through 7.4.5, 7.5.0 through 7.5.3, or 7.6.0 through 7.6.3 AND the File Content Extraction feature is enabled and accessible to users who could exploit the path traversal.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 7.6.3
Interim mitigation

Upgrade FortiSOAR to the latest version as specified by Fortinet's security advisory. If immediate upgrade is not possible, restrict file extraction functionality to trusted users and implement additional input validation on file paths.

Recommended fix Moderate confidence

FortiSOAR 7.3.4, 7.4.6, 7.5.4, or 7.6.4 (or later respective releases)

  1. 1. Identify the current FortiSOAR version by navigating to the FortiSOAR dashboard and checking the version information in the system settings or About section
  2. 2. Based on your current version, plan the upgrade path: if on 7.3.x, upgrade to 7.3.4 or later; if on 7.4.x, upgrade to 7.4.6 or later; if on 7.5.x, upgrade to 7.5.4 or later; if on 7.6.x, upgrade to 7.6.4 or later
  3. 3. Review FortiSOAR upgrade documentation and release notes for your specific version at docs.fortinet.com or through FortiGuard
  4. 4. Create a full backup of the FortiSOAR database and configuration before proceeding with the upgrade
  5. 5. Schedule a maintenance window as upgrades may require system downtime
  6. 6. Perform the upgrade using the FortiSOAR management interface or command line tools as documented
  7. 7. After upgrade, verify the version number has been updated successfully
  8. 8. Test the File Content Extraction functionality to confirm it works correctly post-upgrade
Caveat Standard upgrade risks apply - backup before upgrading, test in non-production environment first, review release notes for any configuration or feature changes between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortisoar Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22573 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22573 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data