CVE-2026-8110
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 · uneditedIncorrect permissions assignment in the agent of Ivanti Endpoint Manager before version 2024 SU6 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 confidenceA local privilege escalation vulnerability exists in the Ivanti Endpoint Manager agent due to incorrect permission assignments. An authenticated local attacker can exploit this to gain elevated privileges on the affected system. The vulnerability is patched in version 2024 SU6 and later.
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<= 2022= 2024CVSS 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.
-
Check Ivanti Endpoint Manager agent versionOpen Control Panel > Programs and Features and look for Ivanti Endpoint Manager, or run 'wmic product get name,version' in Command Prompt to list installed programs and their versionsAffected if Version shows 2022 or earlier, or shows 2024 without Service Update 6 (SU6)
-
Check Windows Services for Ivanti Endpoint ManagerOpen Services (services.msc) or run 'sc query type= service state= all' to find any Ivanti Endpoint Manager related servicesAffected if An Ivanti Endpoint Manager service is installed and running with elevated (System) privileges
-
Check file permissions on Ivanti installation directoryLocate the Ivanti Endpoint Manager installation folder (typically in Program Files or Program Files (x86)), right-click and view Properties > Security to examine permissionsAffected if Authenticated users or non-admin accounts have Write or Modify permissions on service executables or configuration files
You are affected if Ivanti Endpoint Manager agent is installed with version 2022 or earlier, or version 2024 prior to SU6, and the service files have incorrect permissions allowing local privilege escalation.
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 Endpoint Manager agent to version 2024 SU6 or later to remediate this vulnerability.
2024 SU6 (or later)
- 1. Identify the current version of Ivanti Endpoint Manager by checking the agent or console
- 2. Review current configuration and backup the Ivanti Endpoint Manager database and settings
- 3. Download Ivanti Endpoint Manager version 2024 SU6 or a later stable release from the official Ivanti download portal (hub.ivanti.com)
- 4. Apply the upgrade following Ivanti's standard upgrade documentation for your deployment type (server-based or distributed)
- 5. After upgrade, verify the agent version shows 2024 SU6 or later
- 6. Confirm the service runs with correct permissions and no errors in the event logs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-8110 — 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-8110 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