dbcve.org
Secure Access ClientApplication · Ivanti

CVE-2026-7432

HIGH · 7.0 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to after 22.7 or later.
See remediation →
72/100
Remediation priority · Elevated
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 race condition in Ivanti Secure Access Client before 22.8R6 allows a locally authenticated user to escalate privileges to SYSTEM

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

A race condition in Ivanti Secure Access Client prior to version 22.8R6 allows a locally authenticated user to manipulate timing of operations to escalate their privileges to SYSTEM level.

MitigationUpgrade Ivanti Secure Access Client to version 22.8R6 or later to remediate the race condition vulnerability.

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
Secure Access ClientApplication
Affected:<= 22.7= 22.8

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
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify Ivanti Secure Access Client is installed
    Check for the presence of Ivanti Secure Access Client in the system. On Windows, check Program Files for the Ivanti folder, or look for the 'Ivanti Secure Access Client' service in Services console.
    Affected if The application is not found on the system (not vulnerable because not installed)
  2. Locate the installed executable
    Find the main executable file. Common paths include: C:\Program Files\Ivanti\Secure Access Client\IvantiSecureAccessClient.exe or C:\Program Files (x86)\Ivanti\Secure Access Client\. Right-click the executable and select Properties, then check the Details tab for the version information.
    Affected if The executable file does not exist or version information cannot be retrieved
  3. Determine the installed version number
    Read the File Version or Product Version from the executable properties, or run 'IvantiSecureAccessClient.exe --version' if supported. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Ivanti\Secure Access Client for a Version value.
    Affected if Version information cannot be obtained to compare against vulnerable ranges
  4. Compare version to affected ranges
    Compare the installed version to the vulnerable ranges: any version <= 22.7 or exactly version 22.8. Versions 22.8R6 and later are not affected.
    Affected if Installed version is 22.8 or lower (specifically <= 22.7 or exactly 22.8)
  5. Confirm the service is present and accessible
    Open Services console and verify the 'Ivanti Secure Access Client' service exists. The vulnerability requires a locally authenticated user to interact with the service, so the service must be installed and configured.
    Affected if The service is not installed or not configured on the system

A system is affected if Ivanti Secure Access Client is installed with a version <= 22.7 or exactly 22.8, and the service is present on the system.

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 22.7
Interim mitigation

Upgrade Ivanti Secure Access Client to version 22.8R6 or later to remediate the race condition vulnerability.

Recommended fix High confidence

22.8R6 or later

  1. Check current Ivanti Secure Access Client version (likely via 'about' menu or system tray)
  2. Download Ivanti Secure Access Client version 22.8R6 or later from the vendor support portal at hub.ivanti.com
  3. Stop the Ivanti Secure Access Client service if prompted during installation
  4. Install version 22.8R6 using elevated privileges
  5. Restart the client service if not automatically started
  6. Verify the installed version shows 22.8R6 or later

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

Fix this in Secure Access Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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