Idira Endpoint Privilege ManagerApplication · Paloaltonetworks

CVE-2026-45174

HIGH · 7.8 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 26.5.0 or later.
See remediation →
80/100
Remediation priority · High
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
Idira Endpoint Privilege Manager Linux Agent versions prior to 26.5 allow a local attacker to potentially compromise the agent daemon initialization. CyberArk Security Bulletin: CA26-19

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

Idira Endpoint Privilege Manager Linux Agent versions prior to 26.5 contain a vulnerability during agent daemon initialization that allows a local attacker to potentially compromise the daemon. The CVSS 7.8 score indicates high severity likely due to local privilege escalation or integrity impact.

MitigationUpgrade Idira Endpoint Privilege Manager Linux Agent to version 26.5 or later to address the daemon initialization vulnerability.

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
Idira Endpoint Privilege ManagerApplication
Affected:< 26.5.0

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
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 checks

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

  1. Identify if Idira Endpoint Privilege Manager Linux Agent is installed
    Look for the agent daemon process running on the system, typically identifiable via process name related to 'Idira' or 'Endpoint Privilege Manager' or through system service listings (systemctl list-units, ps aux).
    Affected if The agent daemon process is found running on the system.
  2. Determine the installed agent version
    Query the installed package or binary version using the system's package manager (dpkg, rpm) or by running the agent binary with version flags (e.g., --version) if available.
    Affected if The installed version number is lower than 26.5.0.
  3. Verify the daemon is active and enabled
    Check if the Idira agent service is active and enabled at boot using service management commands (systemctl status <service-name>, chkconfig, or similar).
    Affected if The daemon is running (active) and set to start at boot (enabled).

The environment is affected if the Idira Endpoint Privilege Manager Linux Agent is installed, running as a daemon, and the version is below 26.5.0.

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

Upgrade Idira Endpoint Privilege Manager Linux Agent to version 26.5 or later to address the daemon initialization vulnerability.

Recommended fix High confidence

26.5.0 or later

  1. Download Idira Endpoint Privilege Manager Linux Agent version 26.5.0 or later from the official CyberArk distribution channel
  2. Stop the currently running Idira Endpoint Privilege Manager agent service
  3. Upgrade the Linux Agent package to version 26.5.0 or later using the appropriate package manager for your Linux distribution (e.g., rpm, dpkg, or the vendor's installer)
  4. Verify the installation was successful by checking the agent version
  5. Start the Idira Endpoint Privilege Manager agent service
  6. Confirm the agent daemon initializes correctly and is running without errors

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

Fix this in Idira Endpoint Privilege Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45174 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