dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 23 Mar 2026.
Endpoint ManagerApplication · Ivanti

CVE-2026-1603

HIGH · 7.5 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 2024 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges 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
An authentication bypass in Ivanti Endpoint Manager before version 2024 SU5 allows a remote unauthenticated attacker to leak specific stored credential data.

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 confidence

Authentication bypass vulnerability in Ivanti Endpoint Manager prior to version 2024 SU5 enables remote unauthenticated attackers to access and leak specific stored credential data, potentially compromising the endpoint management infrastructure.

MitigationUpgrade Ivanti Endpoint Manager to version 2024 SU5 or later. Additionally, audit and rotate any credentials that may have been exposed, and restrict network access to the management interface as a defensive measure.

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:< 2024= 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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

  1. Confirm Ivanti Endpoint Manager installation
    Check for the Ivanti Endpoint Manager service in Windows Services (service name typically 'Ivanti Endpoint Manager' or 'LDMS') or look for the installation directory under C:\Program Files\Ivanti or C:\Program Files (x86)\Ivanti
    Affected if The software is not installed on the system
  2. Identify installed version
    Open Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\LDMain\Setup or check the application's About/Help dialog. The version is typically displayed as a year (e.g., 2024) with a service update number (e.g., SU5)
    Affected if Unable to determine the version number from registry or application
  3. Compare version to affected range
    Check if the installed version is 2024 (any build without SU5 applied) or any version prior to 2024. Versions 2024 SU5 and later are not affected. If running 2024, verify whether Service Update 5 has been applied by checking the full version string (e.g., 2024.0.5 or similar indicating SU5)
    Affected if Version is 2024 without SU5 applied, or version is prior to 2024 (any 2023, 2022, etc. build)
  4. Verify credential storage feature presence
    Since this vulnerability leaks specific stored credential data, check if the Endpoint Manager has configured or stored any credentials. This can include inventory scanning results, account credentials stored for deployment tasks, or admin passwords stored in the console. Review the credential management or accounts configuration within the Endpoint Manager console
    Affected if Credential storage or account management features are configured and the version is vulnerable

The environment is affected if Ivanti Endpoint Manager is installed with version 2024 without Service Update 5 applied, or any version prior to 2024, and credential storage features are in use.

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 2024 or later
Fixed in 2024
Interim mitigation

Upgrade Ivanti Endpoint Manager to version 2024 SU5 or later. Additionally, audit and rotate any credentials that may have been exposed, and restrict network access to the management interface as a defensive measure.

Recommended fix High confidence

2024 SU5 (Service Update 5) or later

  1. 1. Identify the current version of Ivanti Endpoint Manager by accessing the admin console or checking the installation
  2. 2. Verify the version is before 2024 SU5 (versions prior to and including 2024 are affected)
  3. 3. Download Ivanti Endpoint Manager version 2024 SU5 or later from the official Ivanti download portal
  4. 4. Follow Ivanti's standard upgrade procedure for Endpoint Manager, ensuring proper backups of the database and configuration are created before proceeding
  5. 5. Apply the upgrade in a test environment first to validate functionality
  6. 6. After successful testing, apply the upgrade to production environment
  7. 7. Verify the upgrade completed successfully by checking the version in the admin console
  8. 8. Confirm the authentication bypass vulnerability is resolved by reviewing release notes for SU5

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

Fix this in Endpoint Manager Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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