dbcve.org
FortisoarApplication · Fortinet

CVE-2026-22574

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 Service account password via server address modification in LDAP 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

This vulnerability in FortiSOAR allows authenticated attackers to retrieve service account passwords stored in a recoverable format. The attack exploits LDAP configuration where an attacker can modify the server address to access stored credentials that are not properly hashed or encrypted, only encoded or encrypted with reversible methods.

MitigationUpgrade to FortiSOAR versions 7.5.3, 7.6.5 or later. Until patched, restrict access to users with LDAP configuration permissions and monitor for unauthorized changes to LDAP server 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. Check FortiSOAR version
    Access the FortiSOAR admin console and navigate to the 'About' section or use the CLI command 'system version' to retrieve the installed version number.
    Affected if The installed version is 7.3.0 through 7.5.2, or 7.6.0 through 7.6.4.
  2. Identify if LDAP integration is configured
    Navigate to Administration > Authentication > LDAP in the FortiSOAR UI to list all configured LDAP connectors. Check whether any LDAP servers are defined with service account credentials.
    Affected if LDAP integrations are configured and active with stored service account credentials.
  3. Verify user access to LDAP configuration
    Review user roles and permissions in Administration > Users & Roles. Check which roles have permissions to modify or view LDAP server configurations.
    Affected if Multiple users or roles have LDAP configuration permissions beyond strictly necessary administrators.
  4. Inspect stored credential format in LDAP settings
    Export or view the LDAP server configuration details. Examine whether the service account passwords are stored as encoded/encrypted values rather than hashed values.
    Affected if Service account passwords are stored in a reversible encoding or encryption format within the LDAP configuration.

You are affected if FortiSOAR version falls within 7.3.0-7.5.2 or 7.6.0-7.6.4 AND LDAP integrations with service account credentials are configured with users having access to modify LDAP settings.

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.5.3, 7.6.5 or later. Until patched, restrict access to users with LDAP configuration permissions and monitor for unauthorized changes to LDAP server settings.

Recommended fix Moderate confidence

FortiSOAR 7.6.5 (for 7.6.x users) or FortiSOAR 7.5.3 (for 7.5.x and earlier users); latest 7.6.x release recommended

  1. Identify current FortiSOAR version by checking the About section in the FortiSOAR UI or via CLI: diagnose system version
  2. Determine which version branch is currently in use (7.3.x, 7.4.x, 7.5.x, or 7.6.x)
  3. For FortiSOAR 7.6.0-7.6.4: Upgrade to version 7.6.5 or later
  4. For FortiSOAR 7.5.0-7.5.2: Upgrade to version 7.5.3 or later
  5. For FortiSOAR 7.4.x: Upgrade to 7.5.3 or later (7.4 is end-of-life; migrate to 7.5 or 7.6)
  6. For FortiSOAR 7.3.x: Upgrade to 7.5.3 or later (7.3 is end-of-life; migrate to 7.5 or 7.6)
  7. After upgrade, verify LDAP configuration integrity and ensure no unauthorized modifications exist
  8. Review LDAP server settings to confirm only trusted admin accounts have configuration access
Caveat Review release notes for 7.5.3 and 7.6.5 for any configuration or feature changes before upgrading; ensure backup of current configuration

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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