CVE-2026-3277: CWE-312 Cleartext Storage of Sensitive Information in Devolutions PowerShell Universal
The OpenID Connect (OIDC) authentication configuration in PowerShell Universal before 2026.1.3 stores the OIDC client secret in cleartext in the .universal/authentication.ps1 script, which allows an attacker with read access to that file to obtain the OIDC client credentials
AI Analysis
Technical Summary
CVE-2026-3277 is a vulnerability identified in Devolutions PowerShell Universal versions prior to 2026.1.3, involving the insecure storage of sensitive information. Specifically, the OpenID Connect (OIDC) client secret is stored in cleartext within the .universal/authentication.ps1 script file. This practice violates secure credential storage principles and corresponds to CWE-312 (Cleartext Storage of Sensitive Information). An attacker who gains read access to this script can retrieve the OIDC client secret, which is a critical credential used for authentication with identity providers. The vulnerability requires the attacker to have local file read access, which could be achieved through other means such as compromised user accounts or lateral movement within a network. The CVSS v3.1 score is 5.5 (medium severity), reflecting that the attack vector is local (AV:L), with low complexity (AC:L), no privileges required (PR:N), but user interaction is needed (UI:R). The impact is high on confidentiality (C:H) but does not affect integrity or availability. No known exploits have been reported in the wild, and no patches are explicitly linked, but upgrading to version 2026.1.3 or later is recommended. This vulnerability can lead to unauthorized access to authentication credentials, potentially enabling further compromise of systems relying on OIDC authentication configured via PowerShell Universal.
Potential Impact
The primary impact of CVE-2026-3277 is the compromise of confidentiality due to exposure of the OIDC client secret. If an attacker obtains these credentials, they could impersonate legitimate clients in authentication flows, potentially gaining unauthorized access to systems and services protected by OIDC. This could lead to unauthorized data access, privilege escalation, and lateral movement within an organization’s network. Although the vulnerability does not directly affect system integrity or availability, the compromise of authentication credentials can have cascading effects on security posture. Organizations relying on PowerShell Universal for automation, orchestration, or identity federation may face increased risk of breach. The requirement for local file read access limits the scope somewhat, but in environments where multiple users share access or where attackers have already gained footholds, the risk is significant. The lack of known exploits in the wild suggests limited active exploitation currently, but the vulnerability should be addressed promptly to prevent future attacks.
Mitigation Recommendations
To mitigate CVE-2026-3277, organizations should upgrade Devolutions PowerShell Universal to version 2026.1.3 or later, where the issue is resolved. Until upgrading, restrict access permissions on the .universal/authentication.ps1 script to the minimum necessary users and service accounts, ensuring that unauthorized users cannot read the file. Implement strict file system access controls and audit access to sensitive configuration files. Additionally, consider rotating OIDC client secrets after remediation to invalidate any potentially exposed credentials. Employ network segmentation and least privilege principles to reduce the risk of attackers gaining local file access. Monitor logs for unusual access patterns to authentication files and related services. Finally, educate administrators and users on secure credential management and the risks of storing secrets in cleartext.
Affected Countries
United States, Canada, United Kingdom, Germany, France, Australia, Japan
CVE-2026-3277: CWE-312 Cleartext Storage of Sensitive Information in Devolutions PowerShell Universal
Description
The OpenID Connect (OIDC) authentication configuration in PowerShell Universal before 2026.1.3 stores the OIDC client secret in cleartext in the .universal/authentication.ps1 script, which allows an attacker with read access to that file to obtain the OIDC client credentials
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-3277 is a vulnerability identified in Devolutions PowerShell Universal versions prior to 2026.1.3, involving the insecure storage of sensitive information. Specifically, the OpenID Connect (OIDC) client secret is stored in cleartext within the .universal/authentication.ps1 script file. This practice violates secure credential storage principles and corresponds to CWE-312 (Cleartext Storage of Sensitive Information). An attacker who gains read access to this script can retrieve the OIDC client secret, which is a critical credential used for authentication with identity providers. The vulnerability requires the attacker to have local file read access, which could be achieved through other means such as compromised user accounts or lateral movement within a network. The CVSS v3.1 score is 5.5 (medium severity), reflecting that the attack vector is local (AV:L), with low complexity (AC:L), no privileges required (PR:N), but user interaction is needed (UI:R). The impact is high on confidentiality (C:H) but does not affect integrity or availability. No known exploits have been reported in the wild, and no patches are explicitly linked, but upgrading to version 2026.1.3 or later is recommended. This vulnerability can lead to unauthorized access to authentication credentials, potentially enabling further compromise of systems relying on OIDC authentication configured via PowerShell Universal.
Potential Impact
The primary impact of CVE-2026-3277 is the compromise of confidentiality due to exposure of the OIDC client secret. If an attacker obtains these credentials, they could impersonate legitimate clients in authentication flows, potentially gaining unauthorized access to systems and services protected by OIDC. This could lead to unauthorized data access, privilege escalation, and lateral movement within an organization’s network. Although the vulnerability does not directly affect system integrity or availability, the compromise of authentication credentials can have cascading effects on security posture. Organizations relying on PowerShell Universal for automation, orchestration, or identity federation may face increased risk of breach. The requirement for local file read access limits the scope somewhat, but in environments where multiple users share access or where attackers have already gained footholds, the risk is significant. The lack of known exploits in the wild suggests limited active exploitation currently, but the vulnerability should be addressed promptly to prevent future attacks.
Mitigation Recommendations
To mitigate CVE-2026-3277, organizations should upgrade Devolutions PowerShell Universal to version 2026.1.3 or later, where the issue is resolved. Until upgrading, restrict access permissions on the .universal/authentication.ps1 script to the minimum necessary users and service accounts, ensuring that unauthorized users cannot read the file. Implement strict file system access controls and audit access to sensitive configuration files. Additionally, consider rotating OIDC client secrets after remediation to invalidate any potentially exposed credentials. Employ network segmentation and least privilege principles to reduce the risk of attackers gaining local file access. Monitor logs for unusual access patterns to authentication files and related services. Finally, educate administrators and users on secure credential management and the risks of storing secrets in cleartext.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- DEVOLUTIONS
- Date Reserved
- 2026-02-26T15:29:18.531Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 69a1b7a632ffcdb8a23ccfc5
Added to database: 2/27/2026, 3:26:30 PM
Last enriched: 3/31/2026, 7:31:00 PM
Last updated: 4/12/2026, 4:02:48 PM
Views: 98
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.