dbcve.org
FortisoarApplication · Fortinet

CVE-2026-22576

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 7.5.3 / 7.6.5 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
A storing passwords in a recoverable format vulnerability in Fortinet FortiSOAR PaaS 7.6.0 through 7.6.4, FortiSOAR PaaS 7.5.0 through 7.5.2, FortiSOAR PaaS 7.4 all versions, FortiSOAR PaaS 7.3 all versions, FortiSOAR on-premise 7.6.0 through 7.6.4, FortiSOAR on-premise 7.5.0 through 7.5.2, FortiSOAR on-premise 7.4 all versions, FortiSOAR on-premise 7.3 all versions may allow an authenticated remote attacker to retrieve passwords for multiple installed connectors via server address modification in connector configuration.

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 · high confidence

FortiSOAR stores connector passwords in a recoverable (reversible) encrypted format rather than using irreversible hashing. An authenticated attacker with access to connector configuration can modify the server address to trigger the system to return plaintext passwords for multiple installed connectors, exploiting the reversible encryption and insufficient authorization checks.

MitigationUpgrade to FortiSOAR versions 7.6.5 or later (or the latest patched release for 7.5 and 7.4 branches). If patching is not immediately feasible, review connector configurations for unauthorized access and restrict administrative access to connector settings.

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.5.3>= 7.6.0, < 7.6.5

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 FortiSOAR version
    Run 'fwmanager -g --get-version' or check the FortiSOAR UI under System > Settings > About to retrieve the installed version number
    Affected if The installed version falls within >= 7.3.0 and < 7.5.3, or >= 7.6.0 and < 7.6.5
  2. Verify connector configuration presence
    Navigate to War Room > Connectors or use the API endpoint '/api/3/connectors' to list installed connectors
    Affected if Any connectors are installed and configured with stored credentials
  3. Check user role permissions for connector settings
    Go to Administration > Users > Roles in the FortiSOAR UI and review which roles have 'Connector' or 'Configuration' permissions enabled
    Affected if Non-administrator users or users beyond the intended scope have access to modify connector configurations
  4. Inspect stored credential encryption format
    Query the FortiSOAR database (typically PostgreSQL) for the ' connectors' table and examine the 'password' or 'encrypted_password' field - look for base64-encoded or encrypted values rather than hashed values
    Affected if Connector passwords are stored in a reversible format (encrypted, base64, or similar) rather than being irreversibly hashed

You are affected if FortiSOAR version is within the vulnerable ranges AND connectors with stored credentials are configured, regardless of whether users have accessed the plaintext passwords.

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 7.5.3 / 7.6.5 or later
Fixed in 7.5.37.6.5
Interim mitigation

Upgrade to FortiSOAR versions 7.6.5 or later (or the latest patched release for 7.5 and 7.4 branches). If patching is not immediately feasible, review connector configurations for unauthorized access and restrict administrative access to connector settings.

Recommended fix High confidence

FortiSOAR 7.6.5 or later (or 7.5.3+ for those staying on the 7.5 branch)

  1. 1. Identify the current FortiSOAR version by checking the system information in the FortiSOAR administration panel.
  2. 2. For systems on version 7.3.x or 7.4.x: Plan migration to version 7.6.5 or later as these branches are no longer explicitly mentioned as fixed.
  3. 3. For systems on version 7.5.0-7.5.2: Upgrade to FortiSOAR version 7.5.3 or later.
  4. 4. For systems on version 7.6.0-7.6.4: Upgrade to FortiSOAR version 7.6.5 or later.
  5. 5. Before upgrading, perform a full backup of the FortiSOAR database and configuration.
  6. 6. Review the FortiSOAR upgrade guide for your deployment type (PaaS or on-premise) for any prerequisites.
  7. 7. Apply the upgrade during a planned maintenance window following standard FortiSOAR upgrade procedures.
  8. 8. After upgrade, verify that connector configurations are intact and retest that passwords are no longer retrievable via the documented attack vector.
Caveat Review release notes for any configuration changes or deprecated features between your current version and the target version; upgrading across multiple minor versions (e.g., 7.3 to 7.6) may require additional migration steps

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

Fix this in Fortisoar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22576 — 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-22576 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