VulnerabilityPublished 27 Feb 2026Updated 30 Mar 2026

CVE-2026-3277: Devolutions PowerShell Universal · Cleartext Storage of Sensitive Information

Affects Devolutions PowerShell UniversalSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.5 Medium : upgrade to 2026.1.3 when convenient.

Data as of 30 Oct 2026, 11:34 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2026.1.3

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Devolutions PowerShell Universal to 2026.1.3.

Affected software

Product	Affected	Fixed in
DevolutionsPowerShell Universal	Affected <2026.1.3	Fixed in 2026.1.3

AI-suggested

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.

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

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.

CWE-312Cleartext Storage of Sensitive Information (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
Implementation · System Configuration · Operation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest.
Implementation · System Configuration · Operation
In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
Attack patterns
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

devolutions.net/security/advisories/DEVO-2026-0006 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Mar 2026, 19:31 UTC

WeaknessesCWE-312

Technical details

References

Community reviews

Related threats