dbcve.org
FortisoarApplication · Fortinet

CVE-2026-21742

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 7.5.3 / 7.6.4 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 cleartext transmission of sensitive information vulnerability in Fortinet FortiSOAR PaaS 7.6.0 through 7.6.3, 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.2, FortiSOAR on-premise 7.5.0 through 7.5.1, FortiSOAR on-premise 7.4 all versions, FortiSOAR on-premise 7.3 all versions may allow an authenticated attacker to view cleartext password in response for Secure Message Exchange and Radius queries, if configured

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

FortiSOAR versions 7.3-7.6 contain a cleartext transmission vulnerability where an authenticated attacker can view passwords in cleartext within API responses when querying Secure Message Exchange or RADIUS authentication configurations, exposing sensitive credentials.

MitigationUpgrade FortiSOAR to vendor-patched versions and verify that Secure Message Exchange and RADIUS configurations are using encrypted communication channels.

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.4

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
    Log into FortiSOAR admin console and navigate to Administration > About, or run 'fwconsole --version' via CLI to determine the installed version number
    Affected if Version is 7.3.0 through 7.5.2, or 7.6.0 through 7.6.3 (versions below 7.5.3 or 7.6.4)
  2. Identify Secure Message Exchange configuration
    Navigate to Administration > Connector Library or Settings > Integrations and look for Secure Message Exchange connector instances. Check if any instances are created and enabled
    Affected if Secure Message Exchange connector is configured with stored credentials
  3. Identify RADIUS authentication configuration
    Navigate to Administration > Authentication > RADIUS or Settings > Authentication Methods to see if RADIUS authentication is enabled with saved credentials
    Affected if RADIUS authentication is configured with stored shared secrets or passwords
  4. Verify API response exposure (optional confirmation)
    Using an authenticated API client, query the Secure Message Exchange or RADIUS configuration endpoints (such as GET /api/connector/<id> or /api/authentication/radius) and inspect whether password fields return plaintext values instead of masked/encrypted values
    Affected if API responses return password values in plaintext rather than masked or encrypted format

User is affected if FortiSOAR version falls within 7.3.0-7.5.2 or 7.6.0-7.6.3 AND Secure Message Exchange or RADIUS authentication configurations with stored credentials are present in the environment

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.4 or later
Fixed in 7.5.37.6.4
Interim mitigation

Upgrade FortiSOAR to vendor-patched versions and verify that Secure Message Exchange and RADIUS configurations are using encrypted communication channels.

Recommended fix High confidence

FortiSOAR 7.5.3 or later; FortiSOAR 7.6.4 or later

  1. Identify the currently installed FortiSOAR version using the system dashboard or CLI
  2. Determine whether your current version falls within affected ranges: 7.3.0-7.5.2 or 7.6.0-7.6.3
  3. Schedule a maintenance window for the upgrade
  4. Back up the FortiSOAR database and configuration before proceeding
  5. Upgrade to FortiSOAR version 7.5.3 or higher (if on 7.3.x-7.5.x line)
  6. Upgrade to FortiSOAR version 7.6.4 or higher (if on 7.6.x line)
  7. Verify the upgrade was successful by checking the system dashboard
  8. Confirm the vulnerability is resolved by testing Secure Message Exchange and Radius query responses
Caveat Review FortiSOAR release notes for the target version to check for compatibility with existing connectors and custom configurations before upgrading

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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