CVE-2026-8992
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 · uneditedAn improper certificate validation vulnerability in Ivanti Secure Access Client before 22.8R6 allows a remote unauthenticated attacker to execute arbitrary code.
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 confidenceAn improper certificate validation vulnerability in Ivanti Secure Access Client versions prior to 22.8R6 allows a remote unauthenticated attacker to execute arbitrary code due to the client failing to properly validate certificates during authentication.
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.8CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify if Ivanti Secure Access Client is installedCheck installed programs list in Control Panel > Programs and Features, or use command: 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Ivanti*"}' on WindowsAffected if Ivanti Secure Access Client appears in the installed programs list
-
Determine the installed version of Ivanti Secure Access ClientLocate the Ivanti Secure Access Client executable (isaC.exe or similar in Program Files), right-click and select Properties > Details to view File Version, or run 'Get-ItemProperty "C:\Program Files\Ivanti\Secure Access Client\isaC.exe" | Select-Object VersionInfo'Affected if File version shows a number less than or equal to 22.7, or exactly 22.8
-
Verify the exact version number matches vulnerable releasesCompare the found version against the affected range: versions <= 22.7 or exactly 22.8 are vulnerable; version 22.8R6 or later is fixedAffected if Version is 22.7.x or lower, or exactly 22.8.x (without the R6 suffix)
If Ivanti Secure Access Client is installed with version <= 22.7 or = 22.8, the TLS certificate validation can be bypassed, allowing MITM attacks and potential arbitrary code execution.
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 · scopedUpgrade Ivanti Secure Access Client to version 22.8R6 or later to remediate the improper certificate validation vulnerability.
22.8R6
- 1. Identify the current version of Ivanti Secure Access Client installed
- 2. Navigate to the Ivanti hub (hub.ivanti.com) to download version 22.8R6 or later
- 3. Review Ivanti's upgrade documentation for Secure Access Client
- 4. Apply the upgrade following vendor-specific deployment procedures
- 5. Verify the installation of version 22.8R6 or later and confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8992 — 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-2026-8992 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