CVE-2025-22454
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 · uneditedInsufficiently restrictive permissions in Ivanti Secure Access Client before 22.7R4 allows a local authenticated attacker to escalate their privileges.
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 confidenceIvanti Secure Access Client before version 22.7R4 contains insufficiently restrictive permissions that allow a locally authenticated attacker to escalate their privileges to higher permission levels on the affected system.
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< 22.7= 22.7CVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Ivanti Secure Access Client installationCheck for the presence of Ivanti Secure Access Client on the system using system inventory tools or the Windows Add/Remove Programs list, macOS Applications folder, or Linux package manager.Affected if The software is installed on the system
-
Determine installed version numberRetrieve the version of Ivanti Secure Access Client. On Windows, this can typically be found in the program's properties under 'Version' in the file details, or via command line tools like 'wmic product get name,version' or PowerShell. On macOS, right-click the application and select 'Get Info'. On Linux, check via the package manager or the application's --version flag if available.Affected if A version number is returned showing the installed software version
-
Compare version against affected rangeCompare your installed version to the affected range. The vulnerability affects versions less than 22.7 and version 22.7 exactly. The fix is available in version 22.7R4 and later.Affected if The installed version is 22.7 or any version earlier than 22.7, or the version is 22.7 without the R4 patch level
You are affected if Ivanti Secure Access Client is installed and the installed version is 22.7 or any earlier version (not 22.7R4 or later).
Generated from the published advisory. Verify against your own configuration.
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 · scoped22.7
Upgrade Ivanti Secure Access Client to version 22.7R4 or later to address the permission vulnerability.
22.7R4
- Identify the current version of Ivanti Secure Access Client installed on the system
- Download Ivanti Secure Access Client version 22.7R4 or later from the official Ivanti support portal
- Follow Ivanti's standard upgrade procedure to apply the update
- Verify the installed version after upgrade to confirm the security patch is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22454 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22454 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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