dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2025-13662

HIGH · 7.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 2024 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Improper verification of cryptographic signatures in the patch management component of Ivanti Endpoint Manager prior to version 2024 SU4 SR1 allows a remote unauthenticated attacker to execute arbitrary code. User Interaction is required.

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

Ivanti Endpoint Manager's patch management component fails to properly verify cryptographic signatures before 2024 SU4 SR1, enabling a remote unauthenticated attacker to execute arbitrary code through malicious patches, contingent on user interaction.

MitigationUpgrade Ivanti Endpoint Manager to version 2024 SU4 SR1 or later to remediate the cryptographic signature verification flaw.

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Determine Ivanti Endpoint Manager version
    Locate the installation directory or check the product About section. Common paths include C:\Program Files\Ivanti\EndpointManager or check the console's System Overview page. Identify the full version string including any SU (Service Update) and SR (Service Release) designations.
    Affected if The version is 2024 without SU4 SR1, or any version before 2024 (e.g., 2023, 2022, earlier). Versions prior to 2024 SU4 SR1 are vulnerable.
  2. Verify patch management component is in use
    Check if the Patch Management module is enabled. In the Ivanti Endpoint Manager console, navigate to Patch > Patch Settings or review the configured patch policies. Alternatively, check the database or configuration files for active patch deployment schedules.
    Affected if Patch Management is enabled and configured to deploy patches to endpoints. The vulnerability requires the patch management component to be active.
  3. Confirm user-facing patch deployment is configured
    Review the patch deployment settings to determine if end-users can initiate or approve patch installations. Check for any user-facing prompts, scheduled patch deployments, or self-service patch portals.
    Affected if Users can interact with patch installation processes (approve, initiate, or receive automated patch deployments). The flaw requires user interaction to trigger the malicious patch execution.

You are affected if Ivanti Endpoint Manager is running version 2024 without SU4 SR1 (or any earlier version) AND the patch management component is enabled with user-accessible patch deployment capabilities.

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 SU4 SR1 or later to remediate the cryptographic signature verification flaw.

Recommended fix High confidence

2024 SU4 SR1

  1. Back up the current Ivanti Endpoint Manager configuration and database before starting the upgrade
  2. Download Ivanti Endpoint Manager version 2024 SU4 SR1 from the official Ivanti download portal
  3. Apply the upgrade to the Endpoint Manager server following standard upgrade procedures
  4. After upgrade completion, verify the patch management component is functioning correctly
  5. Confirm the version shows 2024 SU4 SR1 in the product interface

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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