dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2026-8111

HIGH · 8.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to after 2022 or later.
See remediation →
94/100
Remediation priority · Urgent
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
SQL injection in the web console of Ivanti Endpoint Manager before version 2024 SU6 allows a remote authenticated attacker to achieve remote code execution.

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

SQL injection vulnerability in the web console of Ivanti Endpoint Manager prior to version 2024 SU6 allows a remote authenticated attacker to execute arbitrary SQL queries, which can lead to remote code execution on the affected system.

MitigationApply Ivanti Endpoint Manager version 2024 SU6 or later to remediate the SQL injection vulnerability. If immediate patching is not feasible, restrict network access to the web console and enforce strict authentication controls.

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
Endpoint ManagerApplication
Affected:<= 2022= 2024

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
High
Availability
High

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Ivanti Endpoint Manager version
    Check the installed version through the web console (typically found in Help > About) or by inspecting registry keys or installation logs on the server. Common paths: HKLM\SOFTWARE\Lanir\EndpointManager or C:\Program Files\Ivanti\EndpointManager\
    Affected if The installed version is 2024 (any patch level) or 2022 or earlier (any patch level)
  2. Confirm web console is accessible
    Verify that the Ivanti Endpoint Manager web console (IIS-hosted) is running and reachable. Check IIS Manager for the 'Core' application pool or examine port 443/80 listeners on the server.
    Affected if The web console is enabled and reachable (required for exploitation)
  3. Check network exposure of the web console
    Review firewall rules, IIS bindings, or network perimeter configurations to determine if the web console is exposed to untrusted networks. Examine external-facing IP addresses and port 443/80 access lists.
    Affected if The web console is accessible from untrusted networks or the internet (increases exposure risk)
  4. Verify authentication configuration
    Inspect the Ivanti EPM authentication settings in the web console under Administration > Security or check the coreconfig.xml file in the installation directory for authentication method settings.
    Affected if Authentication is handled locally without strong controls or the default admin account is in use

A user is affected if the installed Ivanti Endpoint Manager version is 2024 (any version) or 2022 or earlier, AND the web console is enabled and accessible, particularly from untrusted networks.

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

Apply Ivanti Endpoint Manager version 2024 SU6 or later to remediate the SQL injection vulnerability. If immediate patching is not feasible, restrict network access to the web console and enforce strict authentication controls.

Recommended fix Moderate confidence

2024 SU6

  1. 1. Create a full backup of the Ivanti Endpoint Manager database and configuration
  2. 2. Review the Ivanti Endpoint Manager 2024 SU6 release notes at hub.ivanti.com for any special requirements or warnings
  3. 3. Download the Ivanti Endpoint Manager 2024 SU6 installer from the Ivanti customer portal
  4. 4. Apply the upgrade during a scheduled maintenance window following Ivanti's official upgrade documentation
  5. 5. Verify the upgrade was successful by logging into the web console
  6. 6. Confirm the SQL injection vulnerability is resolved by verifying the patch version
Caveat Review release notes for any configuration or feature changes that may require adjustments post-upgrade

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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