CVE-2026-45172: Idira PSMP Arbitrary Command Execution – Patch Guidance
Idira Privileged Session Manager for SSH (PSMP) contains a flaw that allows authenticated users with basic system access to run arbitrary commands on the PSMP host itself. An attacker who already has valid credentials and low-level permissions—perhaps a contractor or junior staff member—could exploit incomplete input validation to escalate their privileges and take full control of the session management system. This is particularly dangerous because PSMP systems typically guard access to critical infrastructure and administrative credentials.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 8.8 HIGH · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-78
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-11 / 2026-06-23
NVD description (verbatim)
Due to incomplete input validation in Idira Privileged Session Manager for SSH (PSMP) versions prior to 15.0.2, 14.6.3, 14.2.5, and 14.0.6, an authenticated, low-privileged user could potentially execute arbitrary commands on the PSMP host. CyberArk Security Bulletins: CA26-17 and CA26-18
4 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-45172 is a command injection vulnerability (CWE-78) in Idira PSMP versions before 15.0.2, 14.6.3, 14.2.5, and 14.0.6. The vulnerability stems from inadequate input validation that fails to properly sanitize user-supplied input before passing it to system commands. An authenticated user with low privilege level can craft malicious input that breaks out of the intended command context and executes arbitrary shell commands with PSMP process privileges. The attack requires network access and valid credentials but no user interaction or elevated starting privileges.
Business impact
Successful exploitation compromises the confidentiality, integrity, and availability of the PSMP system. Since PSMP manages privileged SSH sessions and typically stores sensitive credentials and session recordings, an attacker gaining command execution can steal credentials for critical systems, modify or delete audit logs to hide malicious activity, disrupt session management for legitimate users, and potentially pivot to protected systems that PSMP guards access to. The reputational and compliance risks are severe if audit trails are tampered with or if downstream systems are breached via stolen credentials.
Affected systems
Idira Privileged Session Manager for SSH is affected in the following versions: any release prior to 15.0.2 in the 15.x branch, prior to 14.6.3 in the 14.6 branch, prior to 14.2.5 in the 14.2 branch, and prior to 14.0.6 in the 14.0 branch. Organizations must verify their current PSMP version against these fixed versions. Verify exact patch versions against Palo Alto Networks security bulletins CA26-17 and CA26-18.
Exploitability
Exploitability is high among organizations where PSMP is deployed, but the attack requires an authenticated user with valid credentials. The vector is network-based with low attack complexity, meaning an attacker can exploit it remotely without special conditions once authenticated. The absence of KEV status indicates this has not yet been observed in active exploitation campaigns at the time of publication, but the straightforward nature of input validation flaws and the high access level granted by PSMP make this attractive to threats with insider access or those targeting organizations where credential compromise has already occurred.
Remediation
Upgrade Idira PSMP to a patched version immediately: 15.0.2 or later for 15.x deployments, 14.6.3 or later for 14.6 deployments, 14.2.5 or later for 14.2 deployments, or 14.0.6 or later for 14.0 deployments. Verify exact version numbers and any prerequisite steps in Palo Alto Networks security bulletins CA26-17 and CA26-18 before patching. If immediate patching is not feasible, restrict authenticated access to PSMP to trusted accounts only and monitor all command execution logs for anomalous activity.
Patch guidance
Follow Palo Alto Networks' guidance in security bulletins CA26-17 and CA26-18 for detailed patch instructions, including any prerequisites or post-patch validation steps. Organizations running multiple PSMP versions should prioritize upgrading systems on the oldest branch (14.0.x) first, then 14.2.x, 14.6.x, and finally 15.x. Test patches in a non-production environment before deploying to production PSMP systems to ensure session continuity and that no audit functionality is disrupted. Schedule patching during maintenance windows to minimize service interruption.
Detection guidance
Monitor PSMP logs for suspicious command execution patterns, particularly commands that appear to originate from low-privileged user sessions. Look for evidence of shell metacharacters (pipes, semicolons, backticks, command substitution syntax) in input that should be alphanumeric. Enable enhanced logging for all PSMP administrative commands if available. Network-based detection is difficult, but monitoring for unexpected outbound connections from PSMP to external systems may indicate post-exploitation activity. Correlate authentication logs with command execution logs to identify accounts used for exploitation.
Why prioritize this
This vulnerability merits immediate prioritization because it affects a system (PSMP) that is explicitly designed to protect other critical infrastructure, creating a cascading risk. The CVSS score of 8.8 reflects high severity, and the authentication requirement, while limiting exposure, is often a weak control in environments where PSMP is deployed—such systems frequently have shared or contractor accounts. The integrity impact (ability to modify or delete audit logs) is particularly severe in regulated environments. Although KEV status is currently false, the simplicity of input validation exploits means active exploitation is likely once word spreads among threat actors.
Risk score, explained
The CVSS 3.1 score of 8.8 (HIGH) reflects the complete compromise of PSMP confidentiality, integrity, and availability, combined with network-based unauthenticated access and low attack complexity. The requirement for prior authentication (PR:L) prevents a perfect 10.0 but does not materially reduce risk in real-world deployments where internal threats or credential compromise are common. The score appropriately emphasizes that this is a post-authentication privilege escalation with maximum impact on the compromised host.
Frequently asked questions
Does this affect our organization if we're not using Idira PSMP specifically?
Only if your organization runs Idira Privileged Session Manager for SSH. Other session recording or privilege management tools from different vendors are not affected. Check your inventory to confirm whether you use this specific Palo Alto Networks / Idira product.
What if we cannot patch immediately due to business constraints?
Implement access controls immediately: restrict authenticated access to PSMP to a small set of trusted administrative accounts, disable accounts for contractors or users who do not actively need PSMP access, and monitor all login and command execution events in real-time. These are temporary measures only; plan patching as an urgent priority within 1–2 weeks.
Could an attacker use this to steal credentials stored in PSMP?
Yes. If an attacker gains command execution on the PSMP host, they can potentially access credential vaults, session recordings, and audit logs stored there. This is why the business impact of this vulnerability is particularly severe for organizations relying on PSMP to protect their most sensitive systems.
Is there any indication this is being actively exploited?
At the time of publication (June 2026), this vulnerability has not been added to the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning no widespread active exploitation has been publicly reported. However, this does not mean attacks are not occurring; organizations should assume sophisticated threat actors are investigating this flaw.
This analysis is provided for informational purposes to support vulnerability management and security decision-making. SEC.co does not provide legal or compliance advice. Organizations must verify all technical details, patch version numbers, and prerequisites against official Palo Alto Networks security bulletins CA26-17 and CA26-18 before taking remedial action. Patching should be validated in non-production environments first. This analysis does not constitute a guarantee of security or absence of additional vulnerabilities in affected systems. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-0273HIGHPAN-OS Command Injection Allows Root Access via Admin UI
- CVE-2025-41265HIGHWaterfall WF-500 TX Host OS Command Injection (CVSS 7.2)
- CVE-2025-41266HIGHWaterfall WF-500 TX Host Command Injection Vulnerability Analysis
- CVE-2025-41267HIGHWaterfall WF-500 TX Host Command Injection Vulnerability
- CVE-2025-41279HIGHOS Command Injection in Waterfall WF-500 RX Host Administration WebUI
- CVE-2025-41281HIGHWaterfall WF-500 OS Command Injection
- CVE-2025-66273HIGHQNAP Command Injection in QTS and QuTS hero
- CVE-2025-66279HIGHQNAP NAS Command Injection – Admin Authentication Required, HIGH Severity