Idira Privileged Session ManagerApplication · Paloaltonetworks
CVE-2026-45171
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 · uneditedIncomplete input validation and improperly configured folder permissions within Idira Privileged Session Manager (PSM) versions prior to 15.0.3, 14.6.3, 14.2.5, and 14.0.5, an authenticated, low-privileged user could potentially execute arbitrary code. CyberArk Security Bulletin: CA26-17 and CA26-18
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 confidenceIncomplete input validation combined with improperly configured folder permissions in Idira Privileged Session Manager (PSM) allows an authenticated, low-privileged user to execute arbitrary code by exploiting the permission misconfiguration to write to sensitive locations and the input validation flaw to trigger code execution.
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 Privileged Session ManagerApplication
>= 14.0, < 14.0.5>= 14.2, < 14.2.5>= 14.6, < 14.6.3>= 15.0, < 15.0.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Idira PSM versionAccess the PSM administrative interface, typically via web browser to the PSM hostname/IP, navigate to Help > About, or check the installed software package on the host system using system package management toolsAffected if The displayed version falls within any of these ranges: >= 14.0 and < 14.0.5; >= 14.2 and < 14.2.5; >= 14.6 and < 14.6.3; >= 15.0 and < 15.0.3
-
Check PSM folder permissionsReview file system permissions on PSM installation directories (commonly /opt/idira/psm or C:\Program Files\Idira\PSM) and configuration/data folders. Use 'ls -la' on Linux or right-click > Properties > Security on Windows to list permissionsAffected if Any low-privileged or non-administrative user accounts have Write or Modify permissions to sensitive folders such as configuration directories, script libraries, or executable locations
-
Verify folder permission inheritanceExamine whether permission misconfigurations allow authenticated low-privileged users to write to locations where PSM executes code or loads configurations, such as plugin directories, scheduled task folders, or system binary locationsAffected if Low-privileged authenticated users can write files to directories from which PSM loads or executes code
-
Confirm user privilege levelIdentify the privileges of the account being used to access PSM. Check if the account is a standard user without administrative or root privileges within the PSM systemAffected if The account is an authenticated but low-privileged user (non-admin) who can access the PSM interface
A user is affected if their Idira PSM version is below the fixed releases (14.0.5, 14.2.5, 14.6.3, or 15.0.3) AND low-privileged authenticated users have write access to sensitive folders used by PSM.
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 · scoped14.0.514.2.514.6.3
Upgrade Idira PSM to version 15.0.3, 14.6.3, 14.2.5, or 14.0.5 (or later) to address the input validation and folder permission vulnerabilities.
Upgrade to 14.0.5+ (for 14.0.x branch), 14.2.5+ (for 14.2.x branch), 14.6.3+ (for 14.6.x branch), or 15.0.3+ (for 15.0.x branch)
- Identify the currently installed Idira Privileged Session Manager version using the product's version check mechanism
- Determine which version branch your current installation belongs to (14.0.x, 14.2.x, 14.6.x, or 15.0.x)
- For version 14.0.x: upgrade to version 14.0.5 or later
- For version 14.2.x: upgrade to version 14.2.5 or later
- For version 14.6.x: upgrade to version 14.6.3 or later
- For version 15.0.x: upgrade to version 15.0.3 or later
- Obtain the upgrade package from the official CyberArk vendor distribution channels
- Follow CyberArk's standard upgrade procedure for PSM, ensuring to backup configuration before upgrading
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Idira Privileged Session Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45171 — 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-45171 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