CVE-2026-1602
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 · uneditedSQL injection in Ivanti Endpoint Manager before version 2024 SU5 allows a remote authenticated attacker to read arbitrary data from the database.
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 · moderate confidenceSQL injection vulnerability in Ivanti Endpoint Manager prior to version 2024 SU5 allows a remote authenticated attacker to execute arbitrary SQL queries and read sensitive data from the underlying database.
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< 2024= 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm Ivanti Endpoint Manager is installedLocate the Ivanti Endpoint Manager application in your environment and verify it is runningAffected if The product is present and operational in the environment
-
Identify the installed versionAccess the product's version information through the administration console, about dialog, or version check featureAffected if Unable to determine the version from product tooling
-
Compare version to affected rangeReview the version number against the affected ranges: versions prior to 2024, or version 2024 prior to SU5Affected if The installed version is 2024 (any build before SU5) or any version earlier than 2024
-
Check if authentication is enabledVerify whether user authentication is configured and active for the Endpoint Manager web interface or APIAffected if Authentication is enabled (this is required for the attacker to exploit the SQL injection)
-
Review database access logsExamine database query logs for unexpected or unauthorized SQL statements originating from the Endpoint Manager service accountAffected if Suspicious or unauthorized SQL queries appear in the logs
You are affected if Ivanti Endpoint Manager is installed with a version earlier than 2024 SU5 (including any 2024 version prior to SU5, or any version below 2024), and the product is accessible to authenticated users.
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 · scoped2024
Upgrade Ivanti Endpoint Manager to version 2024 SU5 or later to apply the security patch.
Ivanti Endpoint Manager 2024 SU5 (Service Update 5) or later
- Identify current Ivanti Endpoint Manager version by checking the console or running coreservice.exe -v
- Confirm if version is before 2024 or is 2024 (any patch level below SU5)
- Download Ivanti Endpoint Manager 2024 SU5 or later from the Ivanti download portal or contact Ivanti support
- Before applying the upgrade, perform a full backup of the database and configuration
- Schedule a maintenance window as the upgrade may require downtime
- Apply the upgrade following Ivanti's standard upgrade documentation for Endpoint Manager
- After upgrade, verify the version shows 2024 SU5 or later
- Test critical functionality to confirm normal operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1602 — 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-1602 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